Skip to content
Server Security Center
KEVcritical10.0

CVE-2026-75650: Adobe Commerce and Magento Improper Neutralization of Special Elements Used in a Template Engine

Adobe Commerce and Magento · listed in the CISA catalog of actively exploited vulnerabilities since 2026-09-08.

CVSS v3.1 (CVE record)
10.0
critical
EPSS (exploit probability, 30 days)
99.3%
among the highest 0.1% of all CVEs
Added to CISA KEV
2026-09-08
US federal due date 2026-09-11
Automatable (CISA SSVC)
yes
technical impact: total

CVE-2026-75650 explained

CVE-2026-75650 is a template engine injection flaw (CWE-1336) in Adobe Commerce, Adobe Commerce B2B and Adobe Magento Open Source. It can lead to arbitrary code execution without authentication or user interaction. CISA lists it as known to be exploited, which makes patching or mitigating affected stores urgent.

Impact

A remote, unauthenticated attacker can execute arbitrary code in the context of the current user over the network, with low attack complexity and no user interaction. Scope is changed, so impact can extend beyond the vulnerable component. Confidentiality, integrity and availability are all highly affected. CISA rates it automatable with total technical impact, meaning attackers can exploit it at scale and gain full control of the affected component.

Who is affected

The CVE record lists Adobe Commerce up to and including 2.4.4-2026-aug, 2.4.5-2026-aug, 2.4.6-2026-aug, 2.4.7-2026-aug, 2.4.8-2026-aug and 2.4.9-2026-aug; Adobe Commerce B2B up to and including 1.3.3-2026-aug, 1.3.4-2026-aug, 1.4.2-2026-aug, 1.5.2-2026-aug and 1.5.3-2026-aug; and Adobe Magento Open Source up to and including 2.4.6-2026-aug, 2.4.7-2026-aug, 2.4.8-2026-aug and 2.4.9-2026-aug. The CVE record names no fixed version for any of these products.

Written with AI from the data on this page and checked against it automatically.

Official description

Adobe Commerce is affected by an Improper Neutralization of Special Elements Used in a Template Engine vulnerability that could result in arbitrary code execution in the context of the current user. An attacker could exploit this vulnerability to execute arbitrary code.

Exploitation of this issue does not require user interaction. Scope is changed.

CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Adobe Commerce
    Affected
    • ≤ 2.4.4-2026-aug
    • ≤ 2.4.5-2026-aug
    • ≤ 2.4.6-2026-aug
    • ≤ 2.4.7-2026-aug
    • ≤ 2.4.8-2026-aug
    • ≤ 2.4.9-2026-aug
    Fixed in
    not stated
  • Adobe Commerce B2B
    Affected
    • ≤ 1.3.3-2026-aug
    • ≤ 1.3.4-2026-aug
    • ≤ 1.4.2-2026-aug
    • ≤ 1.5.2-2026-aug
    • ≤ 1.5.3-2026-aug
    Fixed in
    not stated
  • Adobe Magento Open Source
    Affected
    • ≤ 2.4.6-2026-aug
    • ≤ 2.4.7-2026-aug
    • ≤ 2.4.8-2026-aug
    • ≤ 2.4.9-2026-aug
    Fixed in
    not stated

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: helpx.adobe.com/security/products/magento/apsb26-146.html
  • CISA's deadline for US federal agencies: 2026-09-11 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Check the Adobe security advisory for the patched release or hotfix for your Commerce, Commerce B2B or Magento Open Source branch.
  2. Apply the vendor's update or mitigations as soon as possible, following CISA's required action.
  3. Restrict network access to administrative and non-public endpoints of affected stores where possible.
  4. Review affected servers for signs of compromise, such as unexpected files, processes or admin accounts.
  5. If no mitigation is available for your deployment, follow CISA's guidance and consider discontinuing use until one is.

The CVE record names no fixed version, which does not mean no fix exists. Consult the Adobe security advisory for patched releases or hotfixes. CISA requires applying mitigations per vendor instructions, following BOD 26-04 guidance for cloud services, or discontinuing use of the product if mitigations are unavailable. Meanwhile, limit internet exposure and check for signs of compromise.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-1336 Improper Neutralization of Special Elements Used in a Template Engine (CWE-1336)

Questions about CVE-2026-75650

Is CVE-2026-75650 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-09-08, with a US federal due date of 2026-09-11. Whether it is used in ransomware campaigns is listed as unknown.
Does an attacker need an account or user interaction?
No. The CVSS data shows no privileges and no user interaction are required, and the attack works over the network with low complexity.
Which version should I upgrade to?
The CVE record does not name a fixed version. Use the Adobe security advisory to identify the patched release or hotfix for your product and branch.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.