CVE-2026-75650: Adobe Commerce / Magento template injection RCE, exploited zero-day

Exploited in the wild Critical 10.0 EPSS 3.9% Magento / Adobe Commerce

A template-engine injection flaw in Adobe Commerce and Magento Open Source lets an unauthenticated attacker execute arbitrary code (critical, CVSS 10.0). Adobe released an emergency hotfix on September 7, 2026 (APSB26-146) and states the flaw has been exploited in the wild against Commerce merchants. CISA added it to the Known Exploited Vulnerabilities catalog on 2026-09-08. Adobe requires both the hotfix and a rotation of the encryption key and all credentials it protects.

What do these terms mean? CVE · CVSS score · exploited (KEV) · EPSS · backported fix · all terms

What to do now

  1. Check whether you run Magento / Adobe Commerce and which version (commands below).
  2. Install the fixed version for your system: see “Patch it” below.
  3. Flush the cache. Adobe's credential rotation procedure: enable maintenance mode, disable cron, rotate keys and credentials, flush cache, re-enable cron, disable maintenance mode (Commerce on Cloud: redeploy).
  4. If you cannot patch today, apply the temporary mitigation below and patch as soon as possible.
  5. Because this flaw is being exploited, also check the server for signs of compromise.

Affected and fixed versions

Affected:

Fixed in:

Am I affected?

php bin/magento --version
vendor/bin/magento-patches -n status | grep "39341\|Status"

Patch it

Use the commands for your system. Distribution packages often keep an older version number with the fix backported, so compare with the fixed package versions in the table below, not only with the upstream version.

Debian
not packaged: composer require magento/product-community-edition
Ubuntu
not packaged: composer
RHEL, AlmaLinux, Rocky, Oracle
not packaged: composer
Fedora
not packaged
SUSE / openSUSE
not packaged
Amazon Linux
not packaged: composer
Arch Linux
not packaged
Alpine
not packaged
FreeBSD
not packaged
Built from source
# Download the hotfix ZIP matching your version from Adobe KB 'commerce-apsb26-146'
# (VULN-39341-composer-patches.zip for 2.4.x-2026-aug/-jul and latest -p releases;
#  VULN-39341_248-p3 / _248-p1 / _247-p8 / _247-p5 / _246-p13 / _246-p11 .patch.zip for older ones).
cd /path/to/magento
unzip VULN-39341-composer-patches.zip
patch -p1 < VULN-39341_Hotfix_COMPOSER.patch   # use -p2 if -p1 fails
php bin/magento cache:flush
# Then rotate the encryption key and all credentials (see mitigation).

General update steps for every system are on the Linux and Unix & BSD pages; after updating, see which services to restart.

If you cannot patch yet

CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

https://helpx.adobe.com/security/products/magento/apsb26-146.html ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2026-75650

Related vulnerabilities

Sources

Page generated automatically from official sources on 2026-11-03 18:05 UTC and reviewed by an editor. Always confirm with your vendor's advisory.