CVE-2026-75650

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

Actively exploited (CISA KEV) Critical 10.0 CVSS 3.1

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.

Description as published by the source, in English.

Key facts

Published: 2026-09-07
Last modified: 2026-09-09
Assigned by: psirt@adobe.com
CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Scored by: psirt@adobe.com
Fix available: Yes, see references

Actively exploited

CISA added this vulnerability to the Known Exploited Vulnerabilities catalogue on 2026-09-08, with a remediation deadline of 2026-09-11 for US federal agencies.

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.

Affected products

Vendor	Product	Versions	Status
Adobe	Commerce	< 2.4.4	Affected
Adobe	Commerce	2.4.4	Affected
Adobe	Commerce	2.4.5	Affected
Adobe	Commerce	2.4.6	Affected
Adobe	Commerce	2.4.7	Affected
Adobe	Commerce	2.4.8	Affected
Adobe	Commerce	2.4.9	Affected
Adobe	Commerce B2b	< 1.3.3	Affected
Adobe	Commerce B2b	1.3.3	Affected
Adobe	Commerce B2b	1.3.4	Affected
Adobe	Commerce B2b	1.4.2	Affected
Adobe	Commerce B2b	1.5.2	Affected
Adobe	Commerce B2b	1.5.3	Affected
Adobe	Magento	< 2.4.6	Affected
Adobe	Magento	2.4.6	Affected
Adobe	Magento	2.4.7	Affected
Adobe	Magento	2.4.8	Affected
Adobe	Magento	2.4.9	Affected

Weakness type

CWE-1336: Improper Neutralization of Special Elements Used in a Template Engine
The product uses a template engine to insert or process externally-influenced input, but it does not neutralize or incorrectly neutralizes special elements or syntax that can be interpreted as template expressions or ot…

References

https://helpx.adobe.com/security/products/magento/apsb26-146.html Patch, Vendor Advisory
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-75650 US Government Resource

Related at Berigo

Articles

A zero day in Magento was exploited for three days before Adobe shipped a fix Mentions this CVE 2026-09-26
Sansec has seen active exploitation of CVE-2026-75650 in Magento Open Source and Adobe Commerce since 4 September 2026. The flaw scores a maximum 10.…
Almost a third of this week's listed vulnerabilities have no severity score Same product 2026-08-25
The weekly vulnerability summary from CISA lists 3882 vulnerabilities for the week beginning 10 August. 1184 of them have no calculated severity scor…
Adobe fixes critical flaw scoring 10.0 in Campaign Classic Same product 2026-08-03
Adobe published an update on 29 July 2026 for two vulnerabilities in Campaign Classic. CVE-2026-48449 scores 10.0 and can give code execution without…
Adobe patches twelve vulnerabilities in ColdFusion and Campaign Classic Same product 2026-06-30
Adobe has published updates fixing twelve CVEs in ColdFusion and Adobe Campaign Classic, several allowing arbitrary code execution.

Does this affect you?

A vulnerability matters only if you run the product, in an affected version, somewhere an attacker can reach.

Check your asset list Browse all vulnerabilities

Sources and freshness

CVE

What it is: A reference number naming one specific vulnerability, for example CVE-2024-9474.
What it tells you: Which vulnerability we are talking about, and in which product.
What it does NOT tell you: Nothing about how serious it is, whether anyone is exploiting it, or whether it concerns you.
Why it matters: Without a shared number, vendor, authority and tooling cannot discuss the same flaw.
Used with the others: The number is the key. NVD, KEV and EPSS all describe the same CVE.

NVD CWE CISA KEV EPSS

How to read this together

No single value should be used on its own. A high CVSS score does not mean a vulnerability is being exploited, and a low one does not mean it is harmless. The four sources answer four different questions.

CVE names the specific vulnerability.
NVD adds severity and technical detail about it.
CWE describes the type of mistake behind it.
CISA KEV shows that it is already being exploited.
EPSS estimates how likely exploitation is soon.

The order that decides what is urgent

Do you actually have the product?
Is the version you run affected?
Is it listed in CISA KEV?
Does it have a high EPSS score?
Is the system reachable from the internet or from others?
How important is the system to the business?
Are there compensating controls already in place?

The first two questions are not about the vulnerability at all. They are about you, and they remove most of the list before you start.

A short example

Fix this week

CVSS 6,5 (medium)

In CISA KEV: yes
EPSS: 94 per cent
A firewall facing the internet

Can be scheduled

CVSS 9,8 (critical)

In CISA KEV: no
EPSS: 0,04 per cent
A test server with no internet access

Sorted by CVSS alone, the one on the right comes first. It is the more serious flaw in theory. But the one on the left is being used against real organisations right now, and it sits where an attacker can reach it. That is the one to fix first.

The critical one still has to be fixed. It just does not have to be fixed today.

This product uses the NVD API but is not endorsed or certified by the NVD. CVE and the CVE logo are registered trademarks of The MITRE Corporation; CVE records are used under the CVE Terms of Use. CWE is a trademark of The MITRE Corporation, used per the CWE Terms of Use. KEV data from CISA (CC0). Exploitation probability from EPSS, a FIRST.org project. Open-source package data from OSV and the GitHub Advisory Database (CC-BY 4.0).

Scores and vectors are shown as published by the sources. The ordering of results is Berigo's own editorial assessment, described on the search page, and is not NVD data. An empty result never means a system is safe.