Adobe Commerce lifecycle policy
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 software support 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.
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. Adobe Commerce quality fixes are not provided. This period is not equivalent to standard or extended support and will not be extended further. Treat it as a migration period, not as a long-term support tier.
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.
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.
Key
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.
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.
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.
Recommended path: migrate to Adobe Commerce as a Cloud Service
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.