Magento 2.4.9 System Requirements
The full stack Magento 2.4.9 needs — PHP 8.4/8.5, MySQL 8.4, OpenSearch 3, Valkey 9 and Varnish 8 — what changed from 2.4.8, and how to check your host is ready before you upgrade.
Magento 2.4.9 GA — Released 12 May 2026
Bundles critical security bulletin APSB26-49. Nine core requirements changed, four of them breaking. Check every component before scheduling your upgrade.
Magento 2.4.9 system requirements at a glance
These are the supported software versions for Magento Open Source and Adobe Commerce 2.4.9, taken from Adobe's official system-requirements documentation. Rows marked as a change from 2.4.8 are the ones most likely to block an upgrade. The requirements are identical for both editions, so they apply equally if you run the licensed edition on Adobe Commerce hosting UK.
| Component | Magento 2.4.9 requirement | Change from 2.4.8 |
|---|---|---|
| PHP | 8.4 or 8.5 | 8.2 dropped · 8.3 upgrade-only |
| MySQL | 8.4 | 8.0 dropped |
| MariaDB | 12.3 (11.8 also) | 10.6 dropped |
| Search engine | OpenSearch 3 | OpenSearch 2.x & Elasticsearch dropped |
| Cache & sessions | Valkey 9 | Redis replaced |
| Full-page cache | Varnish 8 | Varnish 7.x superseded |
| Message queue | RabbitMQ 4.2 or ActiveMQ Artemis 2 | RabbitMQ 3.x superseded |
| Composer | 2.10 | — |
| Web server | nginx 1.30 or Apache 2.4 | — |
Source: Adobe Commerce / Magento Open Source 2.4.9 system requirements (on-premises). Cloud environments differ slightly (e.g. MariaDB 11.8, nginx 1.28). Always confirm against the official Adobe documentation before upgrading.
What changed in Magento 2.4.9
Adobe released Magento Open Source 2.4.9 on 12 May 2026 — the biggest infrastructure shift the platform has seen in years. The release brings 560+ bug fixes, a bundled critical security advisory (APSB26-49), and mandatory upgrades across the server stack. Some components are being retired entirely, not just superseded.
The headline: if your host is still running PHP 8.2, MySQL 8.0, or OpenSearch 2.x, you cannot upgrade to Magento 2.4.9. The store will not run. This is not a configuration problem you can work around — it is a hard requirement at the server level.
The stack baseline was raised across the board — old versions no longer run 2.4.9.
The breaking changes, explained
PHP 8.4 is the recommended production runtime; PHP 8.5 is supported from day one. PHP 8.3 is for the upgrade process only, and PHP 8.2 is dropped. Most shared hosts still default to 8.1 or 8.2.
MySQL 8.4 or MariaDB 12.3 (MariaDB 11.8 is also listed for cloud). MySQL 8.0 and MariaDB 10.6 are dropped. Many managed hosts have not yet moved their database clusters to these versions.
OpenSearch 3 is required. The jump from OpenSearch 2.x to 3 is not trivial, and Elasticsearch is no longer supported in any version. This is the single most common upgrade blocker we see.
Valkey 9 is the new official cache and session store. It keeps Redis wire compatibility, so existing configuration continues to work, but Valkey 9 is the supported and tested path forward.
Varnish 8 is specified for full-page caching. Stores on Varnish 7.x should plan an upgrade — VCL and cache behaviour for 2.4.9 are tested against Varnish 8.
RabbitMQ 4.2 is the supported message broker, with Apache ActiveMQ Artemis 2 now a first-class alternative. Relevant mainly to stores using asynchronous or bulk processing.
Why most hosts aren't ready
Four coordinated breaking changes is a significant ask. For shared and generic managed hosts, these upgrades affect the entire server estate — not just individual accounts. A host that wants to support Magento 2.4.9 needs to upgrade PHP, the database, and OpenSearch across their platform before any single customer can run the new version. That takes time, and many won't have done it yet.
The practical reality for merchants on shared hosting: even if your Magento application is ready to upgrade, you depend on your host finishing their platform upgrades first. If they haven't, you're waiting — or moving.
For stores on dedicated or VPS infrastructure the situation is different. If your host manages your server directly, you can ask them to upgrade each component on a schedule that works for you. That conversation is much easier when your host specialises in Magento — because they already know why you need OpenSearch 3 and what Valkey 9 actually does. See our dedicated Magento hosting UK plans, or the full Magento 2 hosting UK overview.
Don't overlook APSB26-49
Adobe released security bulletin APSB26-49 alongside Magento 2.4.9 on 12 May. The bulletin addresses critical vulnerabilities affecting both Adobe Commerce and Magento Open Source — including arbitrary code execution and arbitrary file-system write. Adobe is not aware of active exploitation of these specific issues, but recommends upgrading as soon as possible.
If you are not yet ready to upgrade to 2.4.9, check whether Adobe has released an isolated security patch for your current version. These patch releases apply the security fixes without requiring the full infrastructure upgrade — read our guides on the May 2026 APSB26-49 patches and the newer July 2026 APSB26-73 update. Apply them now and plan the full 2.4.9 migration for when your hosting environment is ready.
What to ask your host right now
Before you schedule a 2.4.9 upgrade, confirm these six things with your host:
- 1.Do you run PHP 8.4 or 8.5 on my server? (Not just available — actually deployable without a support ticket.)
- 2.Are you on MySQL 8.4 or MariaDB 12.3? If not, what is your upgrade timeline?
- 3.What version of OpenSearch are you running? 3 is required — 2.x is not sufficient, and Elasticsearch is not supported at all.
- 4.Do you support Valkey 9 (or a Redis-compatible store) for cache and sessions?
- 5.Are you running Varnish 8 for full-page caching?
- 6.Can you confirm you have applied, or will apply, the APSB26-49 security patches across your server estate?
EveryHost runs the 2.4.9 reference stack
EveryHost provisions every Magento server to Adobe's reference architecture — PHP 8.4/8.5, OpenSearch 3, Valkey and Varnish — and tracks each component to the version the current release requires, rather than adapting a generic LAMP setup after the fact.
EveryHost stack vs Magento 2.4.9 requirements
If you are an existing EveryHost customer, your server already meets the infrastructure requirements for Magento 2.4.9. You can proceed with the application upgrade at your own pace — no waiting for your host to catch up. If you want us to assist with the upgrade process itself, or you're moving from a host that isn't ready, our free Magento migration service handles the move, or get in touch.
Planning your upgrade
The 2.4.9 release notes describe this as a significant release, not a routine patch. 560+ fixes across the platform mean regression testing takes time. The recommended approach:
Step 1 — Confirm hosting infrastructure
Before anything else, run through the requirement table above with your host. There is no point testing an upgrade on an environment that cannot run 2.4.9.
Step 2 — Apply security patches now
If you're not ready to upgrade to 2.4.9 immediately, apply the APSB26-49 isolated security patches for your current version. These are available for 2.4.6, 2.4.7, and 2.4.8. Don't leave critical vulnerabilities unpatched while you plan the full upgrade.
Step 3 — Test on staging first
Spin up a staging copy of your store on a 2.4.9-compatible environment and run your full test suite. Pay particular attention to third-party extensions — confirm 2.4.9 compatibility with each vendor before upgrading production.
Step 4 — Plan the production upgrade window
Magento upgrades should happen in a low-traffic window with a tested rollback plan. Back the database up offsite before starting. Once you're happy on staging, production is usually straightforward.
Further reading
Frequently asked questions
What are the system requirements for Magento 2.4.9?+
Magento 2.4.9 requires PHP 8.4 or 8.5, MySQL 8.4 or MariaDB 12.3, OpenSearch 3, Valkey 9 (replacing Redis), Varnish 8, RabbitMQ 4.2 or ActiveMQ Artemis 2, Composer 2.10, and nginx 1.30 or Apache 2.4. PHP 8.2, MySQL 8.0, OpenSearch 2.x and Elasticsearch are no longer supported.
What PHP version does Magento 2.4.9 require?+
Magento 2.4.9 runs on PHP 8.4 or PHP 8.5, with 8.4 recommended for production and 8.5 supported from day one. PHP 8.3 is supported for the upgrade process only, and PHP 8.2 is dropped. If your host is still on PHP 8.2 or 8.3, you cannot run 2.4.9 in production.
Does Magento 2.4.9 still support MySQL 8.0?+
No. Magento 2.4.9 drops MySQL 8.0 and MariaDB 10.6. Supported databases are MySQL 8.4 or MariaDB 12.3 (MariaDB 11.8 is also listed for cloud). Many shared hosting providers have not yet upgraded their database servers.
What replaces Redis in Magento 2.4.9?+
Valkey 9 replaces Redis as the official cache and session store. Valkey is an open-source Redis fork that keeps wire compatibility, so existing Redis configuration works, but Valkey 9 is the officially supported option going forward.
What search engine does Magento 2.4.9 require?+
Magento 2.4.9 requires OpenSearch 3. OpenSearch 2.x and Elasticsearch are no longer supported. This is one of the most common upgrade blockers — many hosts still run OpenSearch 2.x or a legacy Elasticsearch instance.
What version of Varnish does Magento 2.4.9 use?+
Magento 2.4.9 specifies Varnish 8 for full-page caching. Stores on Varnish 7.x should plan to upgrade, as VCL and cache behaviour for 2.4.9 are tested against Varnish 8.
Is Magento 2.4.9 a security release?+
In part. Adobe shipped security bulletin APSB26-49 alongside 2.4.9 on 12 May 2026, addressing critical vulnerabilities including arbitrary code execution and arbitrary file-system write. If you cannot upgrade yet, apply the APSB26-49 isolated security patches for your current version.
Already running the 2.4.9 stack
PHP 8.4/8.5, OpenSearch 3, Valkey, Varnish 8 — provisioned to the Adobe reference architecture for Magento. Move to a host that's ready.