Introducing Adobe Commerce 2.4.8

Security Updates

Duo Security 2FA - Updates the Duo Security two-factor authentication (2FA) implementation in Adobe Commerce to use the latest SDK (Web SDK v4). This upgrade enables merchants to transition seamlessly to using Duo Universal Prompt.

Encryption keys - Redesigned managing encryption keys to improve usability and eliminate previous limitations and bugs. New CLI commands are now available for changing keys and re-encrypting certain system configuration, payment, and custom field data.

One-time password (OTP) settings - This update is required to resolve an error that was introduced by a backward-incompatible change in 2.4.7. The description of the OTP Window field now provides an accurate explanation of the setting and the default value has been changed from 1 to 29.

Platform Updates

This release includes key platform upgrades that strengthen Adobe Commerce’s reliability and performance, ensuring it’s fully equipped to support the evolving needs of modern digital commerce.

Cache - This release includes support for Valkey 8.x.

Database - In alignment with our support lifecycle policy, Adobe Commerce is now compatible with the following long-term support (LTS) versions of the following database technologies:

• MariaDB 11.4 LTS _(supported until 2029)_: The previous version (MariaDB 10.6) reaches end-of-life in 2026, making this upgrade essential for maintaining system integrity and performance. MariaDB 10.6 is still supported, but Adobe recommends upgrading to MariaDB 11.4 when upgrading to Adobe Commerce 2.4.8.
• MySQL 8.4 LTS _(supported until 2032)_: The previous version (MySQL 8.0) reaches end-of-life in 2026, making this upgrade essential for maintaining system integrity and performance. MySQL 8.0 is still supported, but Adobe recommends upgrading to MySQL 8.4 when upgrading to Adobe Commerce 2.4.8

This release includes the following database enhancements:

• MySQL collation: The system now defaults to using utf8mb4 collation for MySQL, ensuring compatibility with MySQL 8 and future-proofing against the deprecation of utf8mb3.
• MySQL foreign fey restrictions: MySQL 8.4 introduces stricter foreign key validation by default. The restrict_fk_on_non_standard_key setting is now ON by default, which restricts the use of non-unique or partial keys as foreign keys.

Search - Adobe Commerce is now optimized for OpenSearch 2.19 and is no longer compatible with Elasticsearch. All Elasticsearch 7 and 8 modules and classes are now deprecated in the codebase. Adobe strongly recommends transitioning to OpenSearch for both on-premises and cloud infrastructure deployments to ensure continued support and compatibility.

Message Queue - Adds support for RabbitMQ 4.x. Before upgrading to RabbitMQ 4, Adobe Commerce Cloud and on-premises customers must migrate from classic mirrored queues to quorum queues.

PHP - Latest enhancements including PHP 8.4: This release adds PHP 8.4 compatibility for Adobe Commerce, bundled extensions, and Adobe-owned extensions, services, and tools. PHP 8.3 is still supported. PHP 8.2 is still compatible, but only for upgrade purposes. PHP 8.4 compatibility required breaking changes.

Performance Updates

GraphQL - enhancements for cart and checkout, orders, products and catalog, customers and customer groups, returns, tax and pricing, shipping and billing, security and gift card options.

Indexers - The default indexer mode for all indexers is now Update by Schedule when installing a new version of Adobe Commerce or upgrading from a previous version. The new default ensures that indexers are in the recommended configuration, improving system performance and reducing potential issues.

Product Prices - The system now allows for more efficient bulk updates of tier prices without causing performance issues or site unresponsiveness when using the [`/V1/products/tier-prices`]() REST API endpoint. Previously, updating a large number of prices using this endpoint could result in performance issues and site unresponsiveness

Quality Enhancements

Inventory - The system now operates without the previously hidden dependency from Catalog introduced by InventoryIndexer, ensuring that the product creation, display mode switch, stock status change, and other related functionalities work as expected. Previously, this hidden dependency caused inconsistencies as different entities were synchronized and the indexer used different entities.

Orders - The system now operates without the previously hidden dependency from Catalog introduced by InventoryIndexer, ensuring that the product creation, display mode switch, stock status change, and other related functionalities work as expected. Previously, this hidden dependency caused inconsistencies as different entities were synchronized and the indexer used different entities.