CVE Intelligence
CISA KEV Critical

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

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.

Published Sep 7, 2026 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, NIST National Vulnerability Database, GitHub Security Advisories, CVE Program (cve.org) e CISA ADP · CNA: adobe

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

CISA KEV · Sep 8, 2026 Proofs of concept on GitHub · 6
How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • Public exploit/PoC (github)+6
  • EPSS 3.9% (30-day exploitation probability)+14
  • Technical severity (critical)+10
  • Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Confirmed
CISA KEV, listed Sep 8, 2026
EPSS FIRST
3.95%
ahead of 90% of scored CVEs · Oct 14, 2026
Affects
Adobe
Commerce and 3 more
CVSS base
10.0
Critical · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Active
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — helpx.adobe.com (NIST National Vulnerability Database)

CISA required action CISA

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.

US federal deadline: Sep 11, 2026 — passed 34 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Adobe Commerce, Adobe Commerce B2b, Adobe Magento…).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  4. Apply the fixed version or the patch documented under Remediation.
  5. EPSS ahead of 90% of scored CVEs: prioritize it in the patch queue.
  6. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Adobe Commerce < 2.4.4version 2.4.4version 2.4.4-p1version 2.4.4-p10version 2.4.4-p11version 2.4.4-p12version 2.4.4-p13version 2.4.4-p14
and 73 more version 2.4.4-p15version 2.4.4-p16version 2.4.4-p17version 2.4.4-p18version 2.4.4-p2version 2.4.4-p3version 2.4.4-p4version 2.4.4-p5version 2.4.4-p6version 2.4.4-p7version 2.4.4-p8version 2.4.4-p9version 2.4.5version 2.4.5-p1version 2.4.5-p10version 2.4.5-p11version 2.4.5-p12version 2.4.5-p13version 2.4.5-p14version 2.4.5-p15version 2.4.5-p16version 2.4.5-p17version 2.4.5-p2version 2.4.5-p3version 2.4.5-p4version 2.4.5-p5version 2.4.5-p6version 2.4.5-p7version 2.4.5-p8version 2.4.5-p9version 2.4.6version 2.4.6-p1version 2.4.6-p10version 2.4.6-p11version 2.4.6-p12version 2.4.6-p13version 2.4.6-p14version 2.4.6-p15version 2.4.6-p2version 2.4.6-p3version 2.4.6-p4version 2.4.6-p5version 2.4.6-p6version 2.4.6-p7version 2.4.6-p8version 2.4.6-p9version 2.4.7version 2.4.7-b1version 2.4.7-b2version 2.4.7-beta3version 2.4.7-p1version 2.4.7-p10version 2.4.7-p2version 2.4.7-p3version 2.4.7-p4version 2.4.7-p5version 2.4.7-p6version 2.4.7-p7version 2.4.7-p8version 2.4.7-p9version 2.4.8version 2.4.8-beta1version 2.4.8-beta2version 2.4.8-p1version 2.4.8-p2version 2.4.8-p3version 2.4.8-p4version 2.4.8-p5version 2.4.9version 2.4.9-alpha1version 2.4.9-alpha2version 2.4.9-alpha3version 2.4.9-beta1
Vulnerable NIST National Vulnerability Database
Adobe Commerce ≤ 2.4.9-2026-aug, 2.4.8-2026-aug, 2.4.7-2026-aug, 2.4.6-2026-aug, 2.4.5-2026-aug, Vulnerable CVE Program (cve.org) e CISA ADP
Adobe Commerce B2b < 1.3.3version 1.3.3version 1.3.3-p1version 1.3.3-p10version 1.3.3-p11version 1.3.3-p12version 1.3.3-p13version 1.3.3-p14
and 52 more version 1.3.3-p15version 1.3.3-p16version 1.3.3-p17version 1.3.3-p18version 1.3.3-p2version 1.3.3-p3version 1.3.3-p4version 1.3.3-p5version 1.3.3-p6version 1.3.3-p7version 1.3.3-p8version 1.3.3-p9version 1.3.4version 1.3.4-p1version 1.3.4-p10version 1.3.4-p11version 1.3.4-p12version 1.3.4-p13version 1.3.4-p14version 1.3.4-p15version 1.3.4-p16version 1.3.4-p17version 1.3.4-p2version 1.3.4-p3version 1.3.4-p4version 1.3.4-p5version 1.3.4-p6version 1.3.4-p7version 1.3.4-p8version 1.4.2version 1.3.4-p9version 1.5.3-beta1version 1.5.3-alpha3version 1.5.3-alpha2version 1.5.3-alpha1version 1.5.3version 1.5.2-p5version 1.5.2-p4version 1.5.2-p3version 1.5.2-p2version 1.5.2-p1version 1.4.2-p9version 1.5.2version 1.4.2-p1version 1.4.2-p10version 1.4.2-p2version 1.4.2-p3version 1.4.2-p4version 1.4.2-p5version 1.4.2-p6version 1.4.2-p7version 1.4.2-p8
Vulnerable NIST National Vulnerability Database
Adobe Commerce B2b ≤ 1.5.3-2026-aug, 1.5.2-2026-aug, 1.4.2-2026-aug, 1.3.4-2026-aug, 1.3.3-2026-aug Vulnerable CVE Program (cve.org) e CISA ADP
Adobe Magento version 2.4.7-p2version 2.4.7-p3version 2.4.7-p4version 2.4.7-p5version 2.4.7-p6version 2.4.7-p7version 2.4.7-p8version 2.4.7-p9
and 36 more version 2.4.8version 2.4.8-beta1version 2.4.8-beta2version 2.4.6-p3version 2.4.8-p1version 2.4.8-p2version 2.4.8-p3version 2.4.8-p4version 2.4.8-p5version 2.4.9version 2.4.9-alpha1version 2.4.9-alpha2version 2.4.9-alpha3version 2.4.9-beta1version 2.4.7-p1< 2.4.6version 2.4.6version 2.4.6-p1version 2.4.6-p10version 2.4.6-p11version 2.4.6-p12version 2.4.6-p13version 2.4.6-p14version 2.4.6-p15version 2.4.6-p2version 2.4.6-p4version 2.4.6-p5version 2.4.6-p6version 2.4.6-p7version 2.4.6-p8version 2.4.6-p9version 2.4.7version 2.4.7-b1version 2.4.7-b2version 2.4.7-beta3version 2.4.7-p10
Vulnerable NIST National Vulnerability Database
Adobe Magento Open Source ≤ 2.4.9-2026-aug, 2.4.8-2026-aug, 2.4.7-2026-aug, 2.4.6-2026-aug Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
10.0 CVSS 3.1 Critical 3.9 6.0 psirt@adobe.com via NIST National Vulnerability Database
10.0 CVSS 3.1 Critical — — GitHub, Inc. via GitHub Security Advisories
10.0 CVSS 3.1 Critical — — adobe via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H (score shown at the top: psirt@adobe.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-1336

Other CVEs with this weakness →

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

Listed
Sep 8, 2026
Federal deadline
Sep 11, 2026
passed 34 day(s) ago
Ransomware use
Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

Public exploits, PoCs and detection templates

Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.

Proofs of concept on GitHub

Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 3.95%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Hunt retroactively in logs from before Sep 8, 2026 (KEV listing): exploitation may have started earlier.
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · adobe/adobe commerce, adobe/adobe commerce b2b, adobe/magento open source
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • Affected products added · adobe/commerce, adobe/commerce b2b, adobe/magento
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 10.0
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Added to CISA KEV catalog
    Sep 7, 2026 · CISA
  • CVE published
    Sep 7, 2026 · adobe

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

4 on the record

Elsewhere on this site

Adobe
every CVE for this vendor
2026-09
what else CISA listed that month
CWE-1336
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-95631 Adobe Commerce | Improper Input Validation (CWE-20) 2d
  • CVE-2026-95630 Adobe Commerce | Improper Input Validation (CWE-20) 2d
  • CVE-2026-92908 Adobe Commerce | Incorrect Authorization (CWE-863) 2d
  • CVE-2026-92910 Adobe Commerce | Incorrect Authorization (CWE-863) 2d
  • CVE-2026-92911 Adobe Commerce | Cross-site Scripting (Stored XSS) (CWE-79) 2d
  • CVE-2026-92909 Adobe Commerce | Incorrect Authorization (CWE-863) 2d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-75650 is "Adobe Commerce and Magento Improper Neutralization of Special Elements Used in a Template Engine Vulnerability", rated Critical. It affects Commerce (Adobe); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 10.0 describes technical severity. EPSS 3.95% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.