Adobe Commerce: Improper Neutralization of Special Elements Used in a Template Engine (CVE-2026-75650)
Published In CISA KEV since Sources: BSI
- Actively exploited
- Source: VulnCheck KEV (opens in a new tab), ASD ACSC, CSA/SingCERT How we classify
- Public exploit
What is affected, what to do
This vulnerability allows an attacker to gain full control of affected Adobe Magento instances through remote code execution (RCE). It is actively exploited in the wild, as listed in the CISA KEV catalog. A patch is available, making it imperative to address this vulnerability with the highest priority. All versions of Adobe Magento that have not been updated are affected. Immediate patching of affected systems is strongly recommended to mitigate security risks.
The vulnerability is being actively exploited; treat it as a priority. Update commerce to version 2.4.4, commerce_b2b to version 1.3.3, magento to version 2.4.6. Immediate actions, mitigation and detection rules are in the runbook below.
- Affected
- Adobe Commerce
lte 2.4..2.4.9-2026-aug - Adobe Commerce
lte 2.4..2.4.8-2026-aug - Adobe Commerce
lte 2.4..2.4.7-2026-aug - Adobe Commerce
lte 2.4..2.4.6-2026-aug - Adobe Commerce
lte 2.4..2.4.5-2026-aug - Adobe Commerce
lte *..2.4.4-2026-aug - Adobe Commerce B2B
lte 1.5..1.5.3-2026-aug - Adobe Commerce B2B
lte 1.5..1.5.2-2026-aug - Adobe Commerce B2B
lte 1.4..1.4.2-2026-aug - Adobe Commerce B2B
lte 1.3..1.3.4-2026-aug - Adobe Commerce B2B
lte *..1.3.3-2026-aug - Adobe Magento Open Source
lte 2.4..2.4.9-2026-aug - Adobe Magento Open Source
lte 2.4..2.4.8-2026-aug - Adobe Magento Open Source
lte 2.4..2.4.7-2026-aug - Adobe Magento Open Source
lte *..2.4.6-2026-aug
- Adobe Commerce
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
10.0
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: NVD, CVSS v3
10.0
CVSS v3
Severity Critical on the scale from 0 to 10.
Source: BSI
34.7 %
EPSS score
Elevated — model estimates 10-50% exploitation likelihood.
Source: FIRST EPSS, percentile 98.4
Show all metrics
- Severity
- Critical
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 252.60 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- actively exploitedSource: VulnCheck KEV (opens in a new tab), ASD ACSC, CSA/SingCERT How we classify
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 10.0 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 10.0
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 34.7 %
- Elevated — model estimates 10-50% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 98.4
- Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- Actively exploited
- Published
In CISA KEV since
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- CISA assessment (SSVC)
- Exploitation: active · automatable · Technical impact: total
- Source: CISA Vulnrichment, as of 8 September 2026
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-1336
Response and mitigation
Why act now?
Prioritisation rationale
The flaw is network-reachable, unauthenticated, needs no user interaction and delivers arbitrary code execution with scope change — the same attack surface that TrojanOrders and Magecart campaigns have historically abused for payment skimming, customer-data theft and backdoor deployment. For e-commerce operators under NIS2 scope (retail and KRITIS-adjacent entities handling payments) the risk is amplified because a successful compromise triggers reportable GDPR Art. 33/34 incidents and PCI-DSS breaches. Exploitation likelihood is already elevated and Adobe Commerce CVEs are historically mass-scanned within days of disclosure; treat as P1 with a 24-48 h patch SLA, and if no maintenance window is available, immediately network-isolate the admin backend as a compensating control.
Runbook step 1
Immediate response (0-24 h)
- Deploy the Adobe security bulletin for CVE-2026-75650 across every Adobe Commerce and Magento Open Source instance; target builds are the August-2026 hotfix line (2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, 2.4.9 each with the "-2026-aug" suffix) plus Adobe Commerce B2B 1.5.2/1.5.3-2026-aug. Confirm the final build identifier in the vendor advisory before rollout.
- Immediately restrict the admin panel (
/adminor your custom backend path) via WAF, reverse proxy or iptables to defined admin networks or VPN until the patch is live. - Invalidate all admin sessions (
bin/magento admin:user:unlock, flush session store) and rotate admin passwords plus integration tokens; regenerate API keys stored inenv.phpand in any Adobe Commerce Marketplace integrations. - Set
pub/media,var/andgenerated/to read-only for everyone except the web server user to hinder webshell deposit; usebin/magento maintenance:enableif rollout cannot start within six hours. - Capture a forensic snapshot (filesystem, database, access logs, FPM logs for the last 30 days) before patching — the "scope changed" classification means a compromise may already have pivoted into the host OS or linked services.
Runbook step 2
Mitigation layers
- Network segmentation: keep the Commerce frontend in a DMZ, serve the admin backend only through a separate VLAN behind an MFA-protected jump host; constrain PHP-FPM outbound traffic to an allowlist (Adobe services, payment gateways) to kill C2 and secondary-payload fetches.
- WAF/IPS: virtual patch for POST/PUT against template and email-template endpoints (
/rest/*/V1/*,/graphql,/admin/*/email_template/*); inspect request bodies for suspicious template directives such as{{var ...}},{{block ...}},{{template ...}},getData(,system(,passthru(in unexpected parameters. - Application hardening: enable
template_filter_strict_modeinapp/etc/env.php; shorten admin session lifetime viabin/magento config:set admin/security/session_lifetime; enforceMagento_TwoFactorAuthfor every admin account. - IAM/least privilege: deny the PHP-FPM user write access to
app/etc/env.php; strip the shop database user ofFILE,SUPERandCREATE ROUTINE; use a dedicated admin DB user only for setup jobs. - Endpoint: ship an AppArmor/SELinux profile for
php-fpmthat forbidsexec,curl,wgetand execution from/tmp; extenddisable_functionsinphp.iniwithexec,passthru,shell_exec,system,proc_open,popenwhere shop functionality permits. - CDN/cache layer: put admin and REST API paths behind Fastly/Cloudflare bot management with a per-IP rate limit (e.g. 10 req/min on
/rest/V1/).
Runbook step 3
Detection rules
- Web access log: POST to
/rest/*/V1/*or/graphqlwith HTTP 200 and unusually large bodies (>8 KB) from unexpected geographies; Sigma shape:selection: cs-method: POST, cs-uri-stem|contains: ['/rest/','/graphql'], cs-user-agent|contains: ['python-requests','curl','Go-http-client']. - PHP-FPM process ancestry (Sysmon EID 1 / auditd
execve):php-fpm→sh/bash/python/perl→ network tools (curl,wget,nc); KQL:DeviceProcessEvents | where InitiatingProcessFileName == "php-fpm" and FileName in ("sh","bash","python3","curl","wget","nc"). - Filesystem changes in
pub/,app/code/,generated/code/outside deployment windows — auditd-w /var/www/html/pub -p waplus FIM alerts on new.phpfiles. - Magento admin audit: new admin users, modified
core_config_datarows undersystem/*, new email templates or CMS blocks containing template syntax — SQL audit onINSERT INTO admin_user,UPDATE core_config_data WHERE path LIKE 'system/%'. - Outbound connections from the web server to rare ASNs or to Pastebin/Discord/Telegram APIs (Zeek
conn.log+ssl.logwith SNI allowlist comparison); strong indicator of Magecart or skimmer staging.
- Web access log: POST to
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
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.
Source: BSI WID Portal
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| Adobe | Adobe Commerce |
|
|
| Adobe | Adobe Commerce B2B |
|
|
| Adobe | Magento Open Source |
|
|
| adobe | commerce |
|
|
| adobe | commerce_b2b |
|
|
| adobe | magento |
|
|
| Adobe | Magento |
|
|
Vendors and products
Weakness classes (CWE)
CWE-1336Improper Neutralization of Special Elements Used in a Template Engine
Base
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 other code directives when processed by the engine.
Entry at MITRE CWE-1336
Public exploit references
Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.
| CISA KEV Catalog | CISA Known Exploited Vulnerability (opens in a new tab)cisa.gov | actively exploited | |
| CSA/SingCERT | Active Exploitation of Vulnerability in Adobe Products (opens in a new tab)CSA/SingCERT | actively exploited | |
| ASD ACSC | Active exploitation of Adobe Commerce and Magento Open Source vulnerability (opens in a new tab)ASD ACSC | actively exploited | |
| PoC-in-GitHub (nomi-sec) | CVE-2026-75650 (opens in a new tab)github.com | PoC (publicly reported)reported, not verified | |
| PoC-in-GitHub (nomi-sec) | stylesmuggler (opens in a new tab)github.com | PoC (publicly reported)reported, not verified | |
| PoC-in-GitHub (nomi-sec) | stylesmuggler-ioc-toolkit (opens in a new tab)github.com | PoC (publicly reported)reported, not verified | |
| PoC-in-GitHub (nomi-sec) | stylesmuggler-adobe-patches (opens in a new tab)github.com | PoC (publicly reported)reported, not verified | |
| PoC-in-GitHub (nomi-sec) | stylesmuggler-adobe-patches-mageos (opens in a new tab)github.com | PoC (publicly reported)reported, not verified | |
| PoC-in-GitHub (nomi-sec) | cve-2026-75650-magento-validation-lab (opens in a new tab)github.com | PoC (publicly reported)reported, not verified |
References & sources
- helpx.adobe.comAdobe Commerce and Magento — CVE-2026-75650Vendor advisory, pwn-watch
- cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2026-75650government-resource
- pwn.watchpwn.watch: Adobe Commerce and Magento: Adobe Commerce and Magento Improper Neutralization of Special Elements Used in a Template Engine Vulnerabilitypwn-watch
- NVD (NIST)NVD: CVE-2026-75650pwn-watch
- cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Record modifiedCISA ADP
CISA assessment (SSVC): exploitation: active, automatable: yes
Show the original change
Individual changes of this event as published by NVD Type Action Before After SSVC assessment changed {"id":"CVE-2026-75650","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-09-08T18:44:04.878935Z"}{"id":"CVE-2026-75650","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-09-08T00:00:00+00:00"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
NVD analysis modifiedNVD
Show the original change
Individual changes of this event as published by NVD Type Action Before After Reference type added —CISA-ADP: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-75650 Types: US Government ResourceSource identifier: nvd@nist.gov
Record modifiedCISA ADP
CISA assessment (SSVC): exploitation: active, automatable: yes
Show 2 original changes
Individual changes of this event as published by NVD Type Action Before After Reference added —https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-75650SSVC assessment changed {"id":"CVE-2026-75650","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-09-08T09:45:46.499403Z"}{"id":"CVE-2026-75650","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-09-08T18:44:04.878935Z"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
CISA KEV entry updated9119a7d8…
4 individual changes: Date Added, Due Date, Required Action, Vulnerability Name
Show 4 original changes
Individual changes of this event as published by NVD Type Action Before After Date Added added —2026-09-08Due Date added —2026-09-08Required Action added —2026-09-08Vulnerability Name added —2026-09-08Source identifier: 9119a7d8-5eab-497f-8521-727c672e3725
Initial analysis by NVDNVD
Newly listed as affected:- Adobe Commerce (before 2.4.4; 80 individual versions)
- Adobe Commerce (before 1.3.3; 59 individual versions)
- Adobe Magento (before 2.4.6; 43 individual versions)
Show 4 original changes
Individual changes of this event as published by NVD Type Action Before After Product configuration added —OR *cpe:2.3:a:adobe:commerce:2.4.4:-:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:-:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p1:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:*:*:*:*:*:*:*:* versions up to (excluding) 2.4.4 *cpe:2.3:a:adobe:commerce:2.4.5:p1:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p2:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p2:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p3:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:-:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p4:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p3:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p1:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p4:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p5:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.7:b1:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p5:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p2:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p3:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p6:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p7:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p8:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p9:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.7:b2:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.7:-:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.7:p1:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p4:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p5:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p6:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p6:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p7:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p8:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.7:p2:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p10:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p9:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p7:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.7:beta3:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p11:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.8:beta1:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.7:p3:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p8:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p10:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p12:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p11:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p9:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.7:p4:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.8:beta2:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.7:p5:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.8:-:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p13:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p12:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p10:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p14:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p13:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p11:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.7:p6:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.8:p1:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.9:-:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.9:alpha1:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p15:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p14:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p12:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.7:p7:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.8:p2:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.9:alpha2:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p16:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p15:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p13:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.7:p8:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.8:p3:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.9:alpha3:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.9:beta1:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.8:p4:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.7:p9:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p14:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p15:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p16:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p17:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p18:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p17:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.7:p10:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.8:p5:*:*:*:*:*:*Product configuration added —OR *cpe:2.3:a:adobe:commerce_b2b:1.4.2:p1:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.4.2:p2:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.4.2:-:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p9:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:-:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p10:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:-:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.4.2:p3:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p10:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p11:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p1:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p12:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p2:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p3:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p4:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p5:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p6:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p7:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p8:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p9:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p1:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p11:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p2:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p3:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p4:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p5:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p6:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p7:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p8:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.4.2:p4:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p13:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p12:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.4.2:p5:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.5.2:-:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p14:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p13:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.4.2:p6:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.5.2:p1:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.5.3:alpha1:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:*:-:*:*:*:*:*:* versions up to (excluding) 1.3.3 *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p15:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p14:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.4.2:p7:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.5.2:p2:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.5.3:alpha2:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p16:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p15:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.4.2:p8:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.5.2:p3:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.5.3:alpha3:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.5.2:p4:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.5.3:beta1:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.4.2:p9:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p17:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p16:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p18:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p17:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.4.2:p10:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.5.2:p5:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.5.3:-:*:*:*:*:*:*Product configuration added —OR *cpe:2.3:a:adobe:magento:2.4.6:-:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.6:p2:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.6:p1:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.7:b1:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.6:p4:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.6:p5:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.6:p3:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.7:b2:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.7:p1:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.7:-:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.6:p6:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.7:p2:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.6:p7:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.7:beta3:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.8:beta1:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.7:p3:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.6:p8:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.6:p9:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.7:p4:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.8:beta2:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.6:p10:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.7:p5:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.8:-:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.6:p11:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.7:p6:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.8:p1:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.9:alpha1:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.6:p12:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.7:p7:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.8:p2:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.9:alpha2:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.6:p13:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.7:p8:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.8:p3:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.9:alpha3:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.6:p14:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.7:p9:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.8:p4:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.9:beta1:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:*:*:*:*:open_source:*:*:* versions up to (excluding) 2.4.6 *cpe:2.3:a:adobe:magento:2.4.6:p15:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.7:p10:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.8:p5:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.9:-:*:*:open_source:*:*:*Reference type added —Adobe Systems Incorporated: https://helpx.adobe.com/security/products/magento/apsb26-146.html Types: Patch, Vendor AdvisorySource identifier: nvd@nist.gov
Show 2 older changes
Record modifiedCISA ADP
CISA assessment (SSVC): exploitation: none known, automatable: yes
Show the original change
Individual changes of this event as published by NVD Type Action Before After SSVC assessment added —{"id":"CVE-2026-75650","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-09-08T09:45:46.499403Z"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
ReceivedAdobe
CVSS V3.1: AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Weakness type: CWE-1336
Description added or changed
Show 5 original changes
Individual changes of this event as published by NVD Type Action Before After Description added —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.CVSS added —AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HWeakness type (CWE) added —CWE-1336Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/75xxx/CVE-2026-75650.json">CVE-2026-75650</a>Reference added —https://helpx.adobe.com/security/products/magento/apsb26-146.htmlSource identifier: psirt@adobe.com
Linked CVEs
| Critical | CVE-2026-75650 | Adobe Commerce | Improper Neutralization of Special Elements Used in a Template Engine (CWE-1336) | 10.0 | Actively exploited |
Linked advisories
- StyleSmuggler (CVE-2026-75650): Patchen allein reinigt keinen Magento-ShopNEOSEC article
- October Patch Tuesday roundup: Over 1,400 Microsoft holes to be plugged, including three zero daysCSO Online
- September 2026 Patch Tuesday roundup: Plugs for two zero day holes among almost 1,000 fixes in WindowsCSO Online
- Adobe Patches Over 170 Vulnerabilities, Including Commerce Zero-DaySecurityWeek
- Adobe fixes critical Magento zero-day exploited to backdoor serversBleepingComputer
- Adobe Commerce max-severity bug comes under active attackCSO Online
- Adobe Patches Magento Zero-Day Exploited to Deploy Rust Backdoor and PHP Web ShellThe Hacker News
- Vulnérabilité dans les produits Adobe (08 septembre 2026)CERT-FR (ANSSI)
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-75650"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-75650.svg?lang=en" alt="CVE-2026-75650 – NEOSEC Intel" height="20"></a>