Ecommerce platforms and AI

Adobe Commerce 2.4.10 alpha ships as 2.4.6 leaves regular support

Adobe published Adobe Commerce and Magento Open Source 2.4.10-alpha1 on October 13, 2026. Two months earlier, 2.4.6 left standard support and 2.4.5 left extended support. We cover the alpha highlights, the support dates for every line from 2.4.5 to 2.4.9, the Adobe Commerce on Cloud deadlines that have already passed and what we would plan this quarter.

In short: Adobe Commerce and Magento Open Source 2.4.10-alpha1 came out on October 13, 2026. Version 2.4.6 left standard support on August 11, 2026 and gets security-only fixes until May 31, 2028; 2.4.5 security fixes end May 31, 2027. Keep production on 2.4.9 or a supported 2.4.8 patch and test the alpha on a separate branch.

Intelligize Digital 4 min readAll notes

Adobe Commerce 2.4.10 alpha ships as 2.4.6 leaves regular support

Key points

  • Adobe released 2.4.10-alpha1 on October 13, 2026, with Fastlane by PayPal, Braintree Insights and Varnish 9 compatibility.
  • Standard support for 2.4.6 ended on August 11, 2026, and extended support for 2.4.5 ended the same day.
  • Security-only fixes end on May 31, 2027 for 2.4.5 and on May 31, 2028 for 2.4.6.
  • Adobe Commerce on Cloud projects had to upgrade MariaDB 10.5 and below and RabbitMQ 3.9 and below by October 30, 2026.
On this page

What Adobe released and retired since August

Adobe published 2.4.10-alpha1 on October 13, 2026, according to its released versions page. It is the first pre-release of the next Adobe Commerce and Magento Open Source line. Two months earlier, on August 11, 2026, standard support ended for 2.4.6 and extended support ended for 2.4.5. For a store still on either of those lines, the support dates matter more than the alpha.

There is no 2.4.9 patch yet. The released versions page lists 2.4.9 itself (May 12, 2026) with no patches, and the 2.4.8 security patch notes, updated November 18, 2026, still show 2.4.8-p5 as the newest patch on that line. The last security round was May 12, 2026, when Adobe shipped 2.4.8-p5, 2.4.7-p10, 2.4.6-p15, 2.4.5-p17 and 2.4.4-p18 alongside 2.4.9.

What is in 2.4.10-alpha1

The 2.4.10-alpha1 release notes list these new features:

  • Fastlane by PayPal for guest checkout, where returning shoppers sign in with a one-time code.
  • Braintree Insights, a payment performance report inside the Magento Admin.
  • Swish as a Swedish local payment method in the Braintree extension.
  • Admin screens for country sub-regions such as states and provinces, so new regions appear at checkout without code changes.
  • Optional Symfony L2 cache support that you enable explicitly. The Zend-based cache stays the default.
  • Compatibility with Varnish 9.0.

Developers should read the dependency and API changes before the features. The bootstrap check for the minimum PHP version moves to 8.3. The predis/predis Redis client goes from 2.x to 3.x. GraphQL quote fields for store and quote currency now return ISO currency codes in place of currency objects, and the products query price filter now uses tax-inclusive prices. A headless storefront that reads either of those needs a test pass. The REST product import also rejects negative values in price-type attributes, so an ERP or PIM feed that ever sends a negative price will see those rows fail.

On security, Adobe fixed a gap where a customer token from one website worked on another website in a website-scoped setup, refactored a template with a cross-site scripting risk and updated several npm dependencies, including underscore.js to 1.13.8. We would install the alpha on a throwaway branch with your real extensions to see which vendors break, and keep production on 2.4.9 or a supported 2.4.8 patch.

Support dates for 2.4.5 through 2.4.9

Adobe’s lifecycle policy, updated September 18, 2026, gives each release three years of standard support from general availability. Adobe Commerce customers on 2.4.6 and 2.4.7 get one more year at no added cost. Versions 2.4.4, 2.4.5 and 2.4.6 also get a one-time security-only period, which Adobe says “will not be extended beyond the published dates.”

  • 2.4.5: extended support ended August 11, 2026. Security-only fixes continue until May 31, 2027.
  • 2.4.6: standard support ended August 11, 2026. Extended support runs to August 31, 2027, and security-only fixes to May 31, 2028.
  • 2.4.7: standard support ends May 31, 2027, and extended support ends May 31, 2028.
  • 2.4.8: standard support ends May 31, 2028.
  • 2.4.9: standard support ends May 31, 2029.

Security-only means exactly that: no quality fixes. A checkout bug found next spring on 2.4.5 will not get an Adobe fix. The extended support wording on the policy page is addressed to Adobe Commerce customers, so if you run Magento Open Source we would plan against the standard support dates.

Cloud deadlines that have already passed

Stores on Adobe Commerce on Cloud (the PaaS product) have a second set of dates in the version upgrade enforcement policy, updated October 14, 2026. It covers 2.4.4 through 2.4.9. It does not apply to Adobe Commerce as a Cloud Service or to on-premises installs.

Some third-party services had to be upgraded by October 30, 2026, including MariaDB 10.5 and below and RabbitMQ 3.9 and below. PHP 8.1 and below must be upgraded by May 31, 2027. The application itself must be on the latest version, or migrated to the SaaS product, by June 1, 2027 for 2.4.4 and 2.4.5 and by June 1, 2028 for 2.4.6 and 2.4.7.

Adobe spells out the consequences. Admin access may be suspended while the storefront stays online. Inbound traffic may then be suspended, which takes the storefront offline. If the environment stays non-compliant, Adobe may decommission it, and the policy says the data “will be permanently deleted and cannot be restored.” Merchants who expect to miss a date can ask their account team or Adobe Support for a short extension.

What we would plan this quarter

If you are on 2.4.5 or older, you are on security-only fixes with a fixed end date of May 31, 2027. Scope the upgrade now, because the jump crosses PHP, search and database versions. The 2.4.9 release notes list PHP 8.5 as fully supported, PHP 8.4 for upgrades only and PHP 8.2 and 8.3 as no longer supported. They also add OpenSearch 3.x as the recommended search engine, MariaDB 11.8 and 12.x, and Valkey 9.x as a cache backend.

On Cloud, compare the database and message queue versions in your project configuration with the October 30 list today. That date has passed, so a project still on MariaDB 10.5 or RabbitMQ 3.9 is already outside the policy.

On 2.4.6 or 2.4.7 you have more time, though 2.4.6 no longer gets quality fixes. We would target 2.4.9 over 2.4.8, since its standard support runs to May 31, 2029 and 2.4.10 is still an alpha. Then ask each extension vendor for a 2.4.9 compatible build and a date for 2.4.10 support.

Certifications

Certifications and partner programmes

Intelligize Digital is a registered partner of these platforms and hosts.

  • BigCommerce BigDev CertifiedBigCommerce Certified
  • BigCommerce Certified PartnerBigCommerce Certified
  • Liquid Storefronts for Theme Developers (Shopify Certified)Liquid Storefronts for Theme DevelopersShopify Certified
  • Headless at Shopify for Developers (Shopify Certified)Headless at Shopify for DevelopersShopify Certified
  • Shopify Foundations (Shopify Certified)Shopify FoundationsShopify Certified

Is this job still done by hand in your store?

Tell us the job and the systems it touches. An engineer reads every request, and we aim to reply within one business day.

We save what you type here so we can follow up if you get interrupted.
One file, up to 10 MB: PDF, Word, Excel, CSV, text, PNG or JPG.

An engineer replies within one business day.

What happens next

  1. An engineer replies We aim to reply within one business day, by email.
  2. A free 30-minute audit On a call with an engineer.
  3. A fixed quote Usually within 3 business days of the audit. Nothing is billed before you agree it.

Book a free audit. One form, one reply from an engineer.

Tell us what you are building or fixing. An engineer reads every request and replies within one business day, with a fixed scope, price and dates once we have talked.

Direct
[email protected]
Response time
Within one business day
Cost of asking
Nothing. The first 30-minute audit is free.

An engineer reads every request.