CVE-2026-75650

CRITICAL(10.0)KEVLikely Exploited

Adobe Commerce and Magento Improper Neutralization of Special Elements Used in a Template Engine Vulnerability

Description

CVE-2026-75650 is a maximum-severity template injection vulnerability in Adobe Commerce and Magento that can result in arbitrary code execution in the context of the current user. The flaw is an improper neutralization of special elements used in a template engine, meaning attacker-supplied input reaches template processing where the engine interprets it as syntax rather than data. Exploitation requires no authentication and no user interaction, and the scope is changed, which is why CVE-2026-75650 carries the maximum CVSS score of 10.0. Because Adobe Commerce and Magento run public-facing online shops handling payment and customer data, this template injection vulnerability puts storefronts at direct risk of full compromise; CISA has added it to the Known Exploited Vulnerabilities (KEV) catalog with a remediation deadline of 11 September 2026.

KEV Information

Vendor
Adobe
Product
Commerce and Magento
Date Added
September 8, 2026
Due Date
September 11, 2026
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.

CVSS Score

Vector String
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HOpen in Calculator
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
CHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
Exploitability Score
3.9
Impact Score
6.0

CWEs

Affected Products

VendorProductVersion
adobecommerce< 2.4.4; 2.4.4; 2.4.5; 2.4.6; 2.4.7; 2.4.8; 2.4.9
adobecommerce b2b< 1.3.3; 1.3.3; 1.3.4; 1.4.2; 1.5.2; 1.5.3
adobemagento< 2.4.6; 2.4.6; 2.4.7; 2.4.8; 2.4.9

References

Weakness Type

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

Template injection occurs when a product feeds externally influenced input into a template engine without neutralising the special elements and syntax that the engine interprets, so the input is evaluated as template code instead of being rendered as text. In CVE-2026-75650 attacker-controlled data reaches Adobe Commerce's template processing unneutralised, and the engine evaluates it, turning a content-rendering path into arbitrary code execution on the store.

Learn more: CWE-1336 — Improper Neutralization of Special Elements Used in a Template Engine

Impact Analysis

CVE-2026-75650 reaches the maximum CVSS 3.1 base score of 10.0 because it is remotely exploitable over the network with low attack complexity, no authentication, no user interaction, and a CHANGED scope — the code execution affects resources beyond the vulnerable template component. Confidentiality, integrity and availability impacts are all High: arbitrary code execution on a commerce platform exposes customer records, order data and stored credentials, allows injection of payment-skimming code into checkout pages, and permits the store to be taken offline. Magecart-style skimming is the concrete danger for e-commerce operators, because a silent code injection into the storefront harvests card data from every subsequent customer without any visible failure. The EPSS score of roughly 2.1% places the vulnerability in the 81st percentile, a strong statistical signal, and CISA's KEV listing confirms exploitation is already happening in the wild.

Exploit Maturity

CISA has confirmed active exploitation of CVE-2026-75650 by adding it to the Known Exploited Vulnerabilities catalog with a remediation deadline of 11 September 2026, which has already passed. The EPSS score of approximately 2.1% places the vulnerability in the 81st percentile, consistent with broad exploitation activity against exposed storefronts. No public exploit code appears among the available references, but Adobe Commerce and Magento vulnerabilities of this class have a strong historical pattern of being weaponised within days of disclosure and integrated into automated scanning by skimming crews, so the absence of a published proof of concept offers no protection. Any store still running an affected version should be treated as likely compromised and triaged for injected payment-skimming code, not merely patched.

Remediation

  1. Follow the CISA KEV required action. Apply mitigations in accordance with Adobe's instructions, comply with CISA's BOD 26-04 "Prioritizing Security Updates Based on Risk" guidance and the "Forensics Triage Requirements", and discontinue use of the product if mitigations are unavailable. The KEV due date was 11 September 2026, so unpatched stores are already past deadline.
  2. Apply Adobe's security patch from APSB26-146. Affected products include Adobe Commerce through 2.4.9 and earlier lines, Adobe Commerce B2B through 1.5.3 and earlier, and Magento Open Source through 2.4.9 — install the hotfix or patched release matching your exact version rather than assuming a recent minor release is safe.
  3. Restrict and monitor the admin and API surface until patched. Limit administrative and web API access to known IP ranges, enable and enforce a WAF in front of the storefront with rules for template-syntax payloads, and rate-limit unauthenticated endpoints that accept free-text input.
  4. Hunt for skimmer code and backdoors. Because arbitrary code execution on a shop is most often monetised through payment skimming, compare all theme templates, JavaScript bundles, .htaccess files and the pub/ and var/ directories against a known-good release, review the database CMS block, CMS page and email-template tables for injected template syntax or script tags, check for unexpected admin accounts and integration tokens, and inspect checkout pages for unauthorised third-party script references.
  5. Harden template handling long term by keeping the template engine in its sandboxed or restricted mode, never passing user-controlled data into template source, validating and encoding external input before it reaches rendering, and maintaining a patch cadence aligned to Adobe's security bulletins — commerce platforms are among the fastest-targeted software after disclosure.

Technical Details

CVE-2026-75650 is a template injection flaw (CWE-1336) in Adobe Commerce and Magento: externally influenced input is passed into the template engine without neutralising the special elements that the engine treats as directives, so instead of being rendered as literal content, the input is parsed and evaluated as template code. Template engines expose object and method access by design, which is why template injection in this class escalates from string evaluation to arbitrary code execution in the context of the current user, as Adobe's advisory describes. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H records that the attack is network-reachable with low complexity, requires neither privileges nor user interaction, and crosses a scope boundary — the changed scope reflects that the executed code escapes the confines of the template subsystem and affects the wider application and host. That combination of unauthenticated reachability and scope change is what drives the score to the 10.0 ceiling.

Frequently Asked Questions

Is CVE-2026-75650 being actively exploited?

Yes. CISA added CVE-2026-75650 to its Known Exploited Vulnerabilities catalog with a remediation due date of 11 September 2026, confirming exploitation in the wild. The EPSS score of about 2.1% places it in the 81st percentile, and Adobe Commerce vulnerabilities of this severity are routinely swept for by automated attack infrastructure.

What products are affected by CVE-2026-75650?

Adobe Commerce is affected in versions up to and including 2.4.9 and all earlier lines, Adobe Commerce B2B up to and including 1.5.3 and earlier versions, and Magento Open Source up to and including 2.4.9. Adobe's security bulletin APSB26-146 lists the exact affected and fixed builds for each product line.

How do I fix CVE-2026-75650?

Apply the patch from Adobe security bulletin APSB26-146 for your exact Commerce, Commerce B2B or Magento version. Because the flaw allows unauthenticated arbitrary code execution, also audit templates, CMS blocks, checkout pages and JavaScript bundles for injected skimmer code and backdoors, and rotate admin credentials and integration tokens.

How severe is CVE-2026-75650?

It is Critical, with the maximum CVSS 3.1 base score of 10.0. The vulnerability is unauthenticated, network-exploitable with low complexity, requires no user interaction, crosses a security scope boundary and yields arbitrary code execution with full confidentiality, integrity and availability impact; with an EPSS score in the 81st percentile and confirmed KEV-listed exploitation, it is an emergency patch for any live store.

CVSS Score

10.0
CRITICAL(10.0)

EPSS Score

EPSS Score99.38%
EPSS Percentile99.9%

Dates

PublishedSeptember 7, 2026
Last ModifiedSeptember 9, 2026
StatusAnalyzed
CVSS Versionv3.1

Need Help With Vulnerability Management?

Our security experts can help you prioritize and remediate vulnerabilities effectively.