Adobe Commerce lifecycle policy

Last update: September 18, 2026

CREATED FOR:

  • Experienced
  • Admin
  • Developer

To streamline the Adobe Commerce lifecycle policy and support the mission-critical needs of customers, Adobe offers a three-year standard support window from the General Availability (GA) date for each version and releases quality fixes during this period. For dates and details on the end of software support for each release, see the End of support dates table.

Adobe does not provide security and quality fixes for third-party services and software dependencies (such as PHP and MySQL) that may reach end of life while customers are in the three-year or extended support period for Adobe Commerce. See the system requirements for a full list of tested and supported third-party technologies.

Standard support

The standard three-year support period from the General Availability (GA) date. Standard support includes quality fixes, security patches, and full Adobe Commerce on-call support.

  • Quality fixes – Customers can access quality fixes by contacting Adobe Commerce Support or through the self-serve Quality Patches Tool.

  • Security fixes – Adobe provides security fixes through cumulative security patches and non-cumulative isolated security patch files for the three-year support period.

  • Hotfixes – For critical security issues, such as zero-day vulnerabilities, Adobe provides hotfixes for all customers on a supported version, even if they are not on the latest patch or security patch release. Note that a hotfix is not comprehensive and does not address all security issues that would be resolved by upgrading to the latest release.

Extended support

Adobe encourages customers to upgrade as soon as possible. However, to provide greater flexibility to align with upgrade plans and business needs, Adobe offers one year of additional support at no additional cost for Adobe Commerce customers on versions 2.4.6 and 2.4.7. The support extension includes quality and security patches for the core application. Extended support for Adobe Commerce 2.4.4 and 2.4.5 versions ends in April and August 2026 as planned.

NOTE
Adobe is introducing an enforced version upgrade policy for Adobe Commerce on Cloud to help every customer stay on a secure, supported platform. Starting June 1, 2027, Adobe will no longer maintain Cloud environments running unsupported Commerce versions and will be forced to take appropriate action to guarantee security of the Adobe Commerce platform and its customers. This includes suspending traffic to the affected infrastructure. As a result, your ecommerce storefront will go offline. If you run on Cloud, you must move to a supported Adobe Commerce version or migrate to Adobe Commerce as a Cloud Service before the published end of extended support date for your release line. If you are on version 2.4.4 through 2.4.9, see the Security and Compliance Notice for the specific actions and deadlines that apply to your environment.

Security-only transitional period

A one-time, time-limited transitional period available only for versions 2.4.4, 2.4.5, and 2.4.6 whose extended support ended in 2025 or 2026. The security-only transitional period provides limited isolated security fixes only (no quality fixes).

IMPORTANT
The security-only transitional period is a one-time exception. It will not be extended beyond the published dates. Treat the security-only period as migration time, not as a long-term support tier. Contact your account team if you’d like help building a migration plan.

End of support dates

The following table shows the full lifecycle for each Adobe Commerce version, including the new version upgrade enforcement dates for Adobe Commerce on Cloud environments.

ReleaseGeneral AvailabilityEnd of standard supportEnd of extended supportEnd of security-only periodSecurity requirements and deadlines (Cloud only)
Adobe Commerce 2.4.9May 12, 2026May 31, 2029TBDN/ATBD
Adobe Commerce 2.4.8April  8, 2025May 31, 2028TBDN/ATBD
Adobe Commerce 2.4.7April  9, 2024May 31, 2027May 31, 2028N/AJune  1, 2028
Adobe Commerce 2.4.6March 14, 2023August 11, 2026August 31, 2027May 31, 2028June  1, 2028
Adobe Commerce 2.4.5August  9, 2022August 12, 2025August 11, 2026May 31, 2027June  1, 2027
Adobe Commerce 2.4.4April 12, 2022April 12, 2025April 14, 2026May 31, 2027June  1, 2027

Support timeline

The support timeline maps support periods quarter by quarter for each Adobe Commerce release line. Use the tables provided earlier in this topic for exact end dates.

2022202320242025202620272028
CommerceQ1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4
2.4.4
2.4.5
2.4.6
2.4.7
2.4.8

Key

Standard support
Extended support
Extended security fixes

Platform dependencies

Staying on a supported Commerce release also requires supported platform dependencies. Adobe does not provide security and quality fixes for third-party services and software dependencies — such as MariaDB, OpenSearch, Redis, Valkey, RabbitMQ, and others — that may reach end of life while you are on the three-year or extended support period for Adobe Commerce. See Shared responsibility security and operational model for details.

You are responsible for maintaining all third-party dependencies and platform services on versions that are actively supported. See System requirements for the full list of tested and supported third-party technologies.

IMPORTANT
Running unsupported dependency versions may result in a security vulnerability on your Cloud instance that Adobe is unable to resolve. In such cases, Adobe will be forced to take appropriate action to maintain the security of the Adobe Commerce platform and its customers. This includes suspending traffic to the affected infrastructure. As a result, your ecommerce storefront will go offline.
If an environment continues to remain non-compliant following traffic suspension, Adobe may terminate cloud services, initiating the decommissioning process. As a result of decommissioning, all data and assets within the hosted ecommerce environment, including all instances, environments, and branches, will be permanently deleted and cannot be restored. See the Required actions and deadlines to secure Commerce environments for how these upgrades are scheduled and the support available to you throughout the process.

PHP end of life and PCI compliance

You are responsible for monitoring the support status of PHP versions used in your environments.

The following PHP versions used by older Commerce release lines have reached or will reach end of life, which has direct implications for PCI compliance.

PHP versionEnd of life dateAffected Commerce versionsPCI compliance impact
PHP 8.1December 31, 20252.4.4, 2.4.5, and 2.4.6 (where PHP 8.1 is used)PCI compliance at risk — running PHP 8.1 past its end-of-life date means security vulnerabilities in PHP may not receive fixes, which puts PCI compliance at risk. Assess compliance status and prioritize upgrading.
PHP 8.2December 31, 20262.4.6 (where PHP 8.2 is used)PCI compliance at risk from end of 2026 — plan upgrade or migration before the end of 2026 to maintain PCI compliance.
IMPORTANT
PCI compliance notice: PCI compliance is the merchant’s responsibility to assess. Adobe strongly recommends that merchants on affected versions consult with their qualified security assessor and prioritize moving to a supported Commerce version and a supported PHP version as soon as possible. For PHP support timelines, see PHP supported versions and PHP end of life.

Upgrade and migration options

If you are on a version approaching or past its end of support dates, take action now. Remaining on an unsupported version puts your store at risk of security vulnerabilities, compliance issues, and loss of support. Adobe provides the following paths to move to a supported release.

Adobe Commerce as a Cloud Service is Adobe’s next-generation hosted commerce platform and Adobe’s recommended long-term destination for all Adobe Commerce on Cloud customers.

  • Adobe manages all infrastructure, patching, and upgrades automatically.
  • You are always on supported, compliant infrastructure — the end-of-life situation does not recur.
  • You get access to Adobe’s latest capabilities: AI-powered merchandising, composable storefront architecture, and native Adobe Experience Cloud integrations.
  • You eliminate recurring upgrade cycles.

Contact your Adobe account team to begin a migration assessment. See Adobe Commerce as a Cloud Service for product overview.

Alternative path: upgrade to a supported Adobe Commerce on cloud or on-premises release

If you cannot migrate to Adobe Commerce as a Cloud Service immediately, you can upgrade to the latest currently supported Adobe Commerce on Cloud release. This moves you to a fully supported, modern infrastructure stack while preserving your existing Commerce on Cloud deployment model.

Note that this path does not eliminate future upgrade obligations. Customers with Adobe Commerce on Cloud deployments must continue upgrading as release lines reach their version upgrade enforcement dates.

Announcements

Get hands-on with agentic AI.

Explore how AI agents work together through real examples and hands-on practice. Join your local User Group to design an agent workflow with your peers and leave with a practical framework you can apply to your own work.

Find an event

Ask AI

Not sure where to start?
Ask me anything about Adobe products.

Type your question or pick a suggestion below.

Use of this AI chatbot is subject to Adobe's Privacy Policy. Don't share sensitive data. AI responses are not your Content, may be inaccurate, and any offers provided are non-binding. Generative AI Terms.

Ask AI