TL;DR: Apply Adobe's security patches for Commerce and Magento immediately per vendor instructions and CISA's BOD 26-04 guidance. If patches cannot be applied, follow CISA's directive to discontinue use or implement mitigations and conduct forensic triage of affected systems.
What Is the Vulnerability?
CVE-2026-75650 is classified as an Improper Neutralization of Special Elements Used in a Template Engine vulnerability (CWE-1336). This class of flaw occurs when user-supplied or externally influenced input is processed by a server-side template engine without adequate sanitization, allowing an attacker to inject and execute arbitrary template directives — and by extension, arbitrary code — on the host system.
The vulnerability resides in Adobe Commerce and Magento Open Source. Adobe's own advisory and the NVD description confirm that successful exploitation results in arbitrary code execution in the context of the current user. Critically, the attack requires no authentication and no user interaction, making it remotely and trivially exploitable by any network-accessible attacker.
The CVSS 3.1 vector string AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H breaks down as follows:
- AV:N — Exploitable over the network
- AC:L — Low attack complexity; no special conditions required
- PR:N — No privileges required
- UI:N — No user interaction required
- S:C — Scope is changed, meaning impact can extend beyond the vulnerable component itself
- C:H / I:H / A:H — High impact on confidentiality, integrity, and availability
The changed scope designation is particularly significant: it indicates that a successful attack can affect resources and components beyond the immediately vulnerable application, amplifying the potential blast radius.
Who and What Is Affected?
The affected products are Adobe Commerce and Magento Open Source. Both are widely deployed e-commerce platforms used by businesses ranging from small retailers to large enterprises. The NVD entry and CISA KEV listing do not restrict the vulnerability to a particular edition — both Commerce (the paid, enterprise-grade product) and Magento Open Source are explicitly named.
Organizations running either platform that have not yet applied the vendor's security updates should treat their installations as potentially compromised, given CISA's confirmation of active exploitation. Key affected groups include:
- Online retailers and merchants running self-hosted Adobe Commerce or Magento Open Source storefronts
- Managed service providers and hosting companies operating Commerce or Magento environments on behalf of clients
- Development and staging environments exposed to the internet that share the same codebase
Because the attack requires no authentication and no user interaction, every internet-accessible instance of the affected software is a potential target regardless of whether it has active customers or transactions.
What Is the Potential Impact?
With a CVSS 3.1 base score of 10.0 (Critical) — the highest possible rating — the potential consequences of exploitation are severe across all three security pillars:
- Confidentiality: An attacker who achieves arbitrary code execution can read sensitive data stored or accessible by the application, including customer records, payment card data, session tokens, API credentials, and database contents.
- Integrity: Attackers can modify application files, inject malicious code into storefront pages (e.g., payment skimmers), alter order and transaction records, or plant persistent backdoors.
- Availability: The application and underlying server can be rendered unavailable through process termination, file deletion, resource exhaustion, or ransomware-style encryption.
The changed scope component of the CVSS vector means that exploitation is not necessarily contained to the web application process. Depending on server configuration, an attacker may be able to pivot to other services, internal network segments, or infrastructure components running on the same host or reachable from it.
CISA has added this vulnerability to the Known Exploited Vulnerabilities (KEV) catalog (added 2026-09-08), confirming that exploitation is occurring in real-world environments. Organizations should treat unpatched systems as actively at risk.
What Should You Do Now?
CISA's required action for this KEV entry is explicit: apply mitigations in accordance with vendor instructions, ensuring compliance with CISA's BOD 26-04 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. The following steps are recommended for all organizations running Adobe Commerce or Magento Open Source:
- Patch immediately. Consult Adobe's official security advisory (available at helpx.adobe.com/security) for the specific patches, versions, or hotfixes addressing CVE-2026-75650. Apply them as your highest priority.
- Identify all instances. Inventory every deployment of Adobe Commerce and Magento Open Source in your environment, including development, staging, and production systems, particularly those internet-accessible.
- Conduct forensic triage. Per CISA's Forensics Triage Requirements referenced in the KEV entry, review server logs, file integrity, and running processes for indicators of compromise — especially on systems that may have been exposed prior to patching.
- Isolate if patching is not immediately possible. If a patch cannot be applied immediately, consider taking the affected storefront offline or placing it behind additional access controls (e.g., WAF rules, IP allowlisting) while remediation is prepared. CISA's guidance states that if mitigations are unavailable, use of the product should be discontinued.
- Review for persistent compromise. Given that this vulnerability allows arbitrary code execution and scope change, verify that no unauthorized files, scheduled tasks, reverse shells, or database modifications were introduced.
- Notify stakeholders. If you are a managed service provider or operate on behalf of clients, inform affected parties promptly so they can assess exposure and initiate their own response procedures.
Federal civilian executive branch (FCEB) agencies are bound by CISA BOD 26-04 patching timelines. All other organizations are strongly encouraged to follow the same prioritization.
How External Testing Surfaces Exposure
Because CVE-2026-75650 is network-accessible, requires no authentication, and has a changed scope, it is a strong candidate for detection through external, black-box security assessment. Point-in-time external vulnerability scanning can help organizations understand their exposure in several ways:
- Version fingerprinting: Scanners that identify the Adobe Commerce or Magento version running on a host can flag installations that fall within the affected version range, even before active exploitation attempts are detected.
- Service enumeration: Identifying which storefronts and admin endpoints are internet-exposed helps prioritize which systems require the most urgent remediation attention.
- Template engine endpoint detection: Security assessments can identify publicly accessible endpoints that interact with template processing logic, surfacing attack surface that may not be immediately obvious from internal architecture diagrams.
- Post-patch verification: After applying vendor patches, a follow-up scan confirms whether the vulnerable version is no longer present and whether any residual indicators of a prior compromise are detectable from the outside.
External testing is not a substitute for patching, but it provides an independent, attacker-perspective view of which assets are reachable and potentially at risk — information that is especially valuable when managing a large or distributed Commerce/Magento estate.
Sources & further reading: NVD CVE-2026-75650 and the CISA KEV catalog are the authority on affected and fixed versions. Vendor/independent analysis: helpx.adobe.com, cisa.gov. This advisory contains no exploit code.
Frequently asked questions
Does an attacker need an account on my Adobe Commerce store to exploit CVE-2026-75650?
No. The CVSS vector for CVE-2026-75650 specifies PR:N (no privileges required) and UI:N (no user interaction required). An unauthenticated attacker with network access to the application can attempt to exploit this vulnerability without any credentials or victim participation.
Is this vulnerability being actively exploited?
Yes. CISA added CVE-2026-75650 to its Known Exploited Vulnerabilities (KEV) catalog on 2026-09-08, which confirms that the vulnerability has been exploited in real-world attacks. Organizations should treat unpatched systems as actively at risk and prioritize remediation immediately.
What does 'changed scope' mean for my environment?
A 'changed scope' (S:C) in the CVSS rating means that a successful exploit can impact resources or components beyond the directly vulnerable Adobe Commerce or Magento application itself. Depending on your server configuration, this could include other services, databases, or systems accessible from the compromised host — amplifying the potential damage beyond the storefront.
Where do I find the official patch from Adobe?
Adobe publishes security bulletins and patches on its official Security Advisories page at helpx.adobe.com/security.html. For CVE-2026-75650, consult the specific bulletin for Adobe Commerce and Magento to identify the correct patch or updated version for your installation. CISA's KEV entry also points to vendor instructions as the authoritative patching guidance.