Magento 2.4.9: Beta1 Features, System Requirements and What's New

What Is Magento 2.4.9?

Magento 2.4.9 is the next major release of both Magento Open Source and Adobe Commerce. It represents the largest architectural shift since Magento 2.4.4, with three foundational framework components replaced and strict new system requirements enforced.

The release follows Adobe's annual May patch cycle. Alpha testing began in June 2025. Beta1 shipped on March 10, 2026. General availability is expected in mid-May 2026.

This is not a routine patch. The framework changes in 2.4.9 affect extensions, hosting infrastructure, and upgrade planning for every Magento merchant.

Magento 2.4.9 Release Timeline

Beta releases receive no official support from Adobe. Test in staging and development environments only. For supported version timelines, current release lines remain under active maintenance:

• 2.4.8: Regular support ends April 11, 2028
• 2.4.7: Regular support ends April 9, 2027

Source: Adobe Commerce Released Versions | Release Schedule

What's New in Magento 2.4.9-Beta1

Framework Modernization

Beta1 replaces three core components that had reached end of life or faced licensing issues:

All Symfony dependencies now target Symfony 7.4 LTS. This is a deep change. Extensions that hook into Laminas MVC classes or TinyMCE JavaScript APIs will need updates before GA.

HugeRTE is an MIT-licensed fork of TinyMCE that maintains basic API compatibility. Simple toolbar extensions run without changes. Complex customizations and deep plugin integrations may need adjustment. Adobe documents the migration path in the Open Source 2.4.9 release notes under "Migrate from TinyMCE to HugeRTE".

Security Fixes (APSB26-05)

The March 10, 2026 security bulletin APSB26-05 patched 17 CVEs across all supported Magento versions:

• 7 Critical severity vulnerabilities (arbitrary code execution, privilege escalation)
• 9 Important severity vulnerabilities
• 1 Moderate severity vulnerability

Alongside beta1, Adobe released security patches for existing versions: 2.4.8-p4, 2.4.7-p9, 2.4.6-p14, 2.4.5-p16, and 2.4.4-p17. Apply these patches now. You do not need to wait for 2.4.9 GA to address these security issues.

Additional security improvements in beta1 include CAPTCHA enforcement on REST and GraphQL account creation endpoints, simplified 2FA configuration (one provider instead of all), and a GraphQL alias limit of 10 per request to prevent resource exhaustion attacks. For more on securing your store, see our security best practices for Magento.

Payment and Shipping Updates

Braintree received the largest expansion:

• Google Pay and Apple Pay accept promotional codes in express checkout
• Apple Pay works on Chrome and Firefox, not limited to Safari
• PayPal Express adds server-side shipping callbacks with real-time cost calculation
• New payment methods: BLIK (Poland), Pay Upon Invoice (Germany), ELO cards (Brazil)
• Real-Time Account Updater refreshes vaulted card details when cards are reissued

USPS migrated from legacy Web Tools XML API to new RESTful APIs with OAuth 2.0 authentication. The legacy API was retired January 25, 2026. Both API modes are available during the transition.

DHL now supports MyDHL RESTful APIs alongside legacy XML.

Fixed Issues and Quality Improvements

Beta1 includes the largest fix count in any 2.4.x release. Adobe Commerce includes all Open Source fixes plus Commerce-specific patches:

Key fix areas include API validation (malformed requests now return 400 instead of 500), checkout handling for special characters, configurable product option persistence, URL rewrite reliability, and multibyte character support in customer group codes.

The bulk async endpoint performance degradation introduced by security patch APSB25-08 is resolved.

Source: Adobe Commerce 2.4.9-beta1 Release Notes

Message Queue: ActiveMQ Artemis Support

Apache ActiveMQ Artemis 2 is now a supported message broker alongside RabbitMQ 4.1. This gives merchants a second production-grade option for asynchronous processing. ActiveMQ uses the STOMP protocol while RabbitMQ uses AMQP. See the ActiveMQ configuration guide for setup details.

Magento 2.4.9 System Requirements

Complete Requirements Table

Source: Adobe Commerce System Requirements

For a complete breakdown across all Magento versions, check our full system requirements guide.

What Changed from 2.4.8

These are the breaking infrastructure changes between Magento 2.4.8 and 2.4.9:

Stores still running MySQL 8.0 or MariaDB 10.6 cannot upgrade to 2.4.9 without database migrations first. Plan these ahead of the GA release.

What Magento 2.4.9 Means for Your Hosting Stack

The system requirements jump in 2.4.9 creates real work for hosting teams. This is not a drop-in upgrade.

Infrastructure Upgrades Required

Database: MySQL 8.0 reaches end of life in April 2026. MariaDB 10.6 was the last LTS from the 10.x line. Both are now dropped. Moving to MySQL 8.4 LTS or MariaDB 11.4 requires testing schema compatibility, replication configs, and stored procedures.

PHP 8.5: First-day support in a Magento release. Hosting environments need PHP 8.5 packages available alongside 8.3 and 8.4 for gradual rollout.

Search: OpenSearch 3.x introduces index format changes from 2.x. Reindexing may be required during the upgrade. This is the largest single-component change for stores with large catalogs.

Message Queue: RabbitMQ 4.1 brings protocol changes from 3.13. Existing queue configurations may need updates. ActiveMQ Artemis offers an alternative for teams invested in the ActiveMQ ecosystem.

Cache and Session: Valkey 8 replaces Redis as the official cache and session store. Redis 7.2 is wire-compatible and may still work, but is no longer in Adobe's official system requirements for 2.4.9.

Web Server: Varnish 7.7 and nginx 1.28 are incremental updates but still require testing VCL configs and server blocks.

Why Managed Hosting Simplifies This Upgrade

With managed Magento hosting, your provider handles infrastructure preparation: PHP version provisioning, database migration support, OpenSearch upgrades, and nginx configuration. This matters in 2.4.9 because the number of simultaneous component upgrades is higher than any recent release.

For stores evaluating their hosting requirements for Magento, the 2.4.9 release makes a strong case for managed infrastructure. Self-managed teams face coordinated upgrades across six or more server components before the Magento upgrade itself can begin.

Extension Compatibility: What to Watch

Laminas MVC Removal

Extensions that extend or override Laminas MVC classes will break. This affects routing, controller dispatching, and request handling. Extension vendors need to migrate to the native PHP MVC layer. Check with your extension providers for 2.4.9 compatibility timelines.

TinyMCE to HugeRTE

Extensions using basic TinyMCE toolbar additions will work with HugeRTE in most cases. Extensions using deep TinyMCE plugin APIs or custom dialog implementations may need rewrites. Test all WYSIWYG-dependent functionality in beta1.

Symfony 7.4 Dependencies

The move to Symfony 7.4 LTS affects cache, HTTP, and event components. Extensions that import Symfony classes below version 7.4 will encounter namespace or method signature changes. Run composer why-not checks against beta1 to identify conflicts early.

How to Test Magento 2.4.9-Beta1

Prerequisites

• PHP 8.3, 8.4, or 8.5
• MySQL 8.4 or MariaDB 11.4
• Composer 2.9.3+
• Magento Marketplace authentication keys (for repo.magento.com access)
• A staging or development environment (never production)

Installation

For a fresh install:

composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition:2.4.9-beta1 magento249beta
cd magento249beta
bin/magento setup:install [your config options]

For existing stores, follow the standard process to upgrade Magento 2 but run it against a staging copy:

composer require magento/product-community-edition:2.4.9-beta1 --no-update
composer update
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento cache:clean

Test extension compatibility, checkout flows, admin functions, and custom module behavior before GA.

FAQ

What is Magento 2.4.9?

Magento 2.4.9 is the next major release of Magento Open Source and Adobe Commerce. Beta1 shipped March 10, 2026 with 501+ fixed issues, three framework modernizations, and updated system requirements. GA is expected mid-May 2026.

When is Magento 2.4.9 GA releasing?

General availability is expected in mid-May 2026, following Adobe's annual May release cycle. Adobe has not confirmed an exact date. Alpha testing started June 2025. Beta1 released March 10, 2026.

What PHP versions does Magento 2.4.9 support?

Magento 2.4.9 supports PHP 8.3, 8.4, and 8.5. PHP 8.2 is no longer supported.

What database versions does Magento 2.4.9 require?

MySQL 8.4 LTS or MariaDB 11.4. Both MySQL 8.0 and MariaDB 10.6 are dropped.

What replaced TinyMCE in Magento 2.4.9?

HugeRTE, an MIT-licensed open-source fork of TinyMCE. The switch happened because TinyMCE 5 and 6 reached end of life and TinyMCE 7 introduced licensing incompatibilities with Magento.

Is Magento 2.4.9-beta1 safe for production?

No. Beta releases are for testing and extension compatibility validation only. Adobe provides no support for beta versions in production environments.

How many issues does Magento 2.4.9-beta1 fix?

501 fixed issues in Magento Open Source and 560 in Adobe Commerce (which includes all Open Source fixes plus Commerce-specific patches). This is the largest fix count in any 2.4.x release.

What is Valkey and why does Magento 2.4.9 support it?

Valkey 8 is an open-source fork of Redis, created after Redis changed its licensing in 2024. Magento 2.4.9 lists Valkey 8 as the official cache and session store, replacing Redis. Redis 7.2 is wire-compatible and may still work, but is no longer in Adobe's official system requirements for 2.4.9.

Will my extensions work with Magento 2.4.9?

Extensions using Laminas MVC, TinyMCE APIs, or older Symfony components will need updates. Contact your extension vendors for 2.4.9 compatibility status. Test all extensions against beta1 before planning your upgrade.

What security vulnerabilities does Magento 2.4.9 fix?

The APSB26-05 bulletin (March 10, 2026) patched 17 CVEs: 7 critical, 9 important, and 1 moderate. Security patches for older versions (2.4.8-p4, 2.4.7-p9, etc.) are available now.

Summary

Magento 2.4.9 is the most significant Magento release in years. The framework modernizations (native PHP MVC, HugeRTE, Symfony Cache) future-proof the platform past PHP 8.5. The strict system requirements (MySQL 8.4 only, MariaDB 11.4 only, OpenSearch 3) mean infrastructure work starts now, not at GA.

Start testing beta1 in staging. Check extension compatibility. Prepare your database migrations. The mid-May 2026 GA will arrive fast.

For stores that want the upgrade handled, managed hosting takes the infrastructure complexity off your plate. Your hosting team prepares the server stack while you focus on testing your store.