Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-75650 – Unauthenticated Remote Code Execution – Adobe Commerce & Magento Open Source (up to

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-75650 is a critical Improper Neutralization of Special Elements Used in a Template Engine vulnerability (CWE-1336) affecting Adobe Commerce, Adobe Commerce B2B, and Magento Open Source. The flaw allows an attacker to execute arbitrary code in the context of the current user without authentication or user interaction. It carries the maximum CVSS v3.1 base score of 10.0 (Critical).

Technical details

  • Root cause: improper neutralization of special elements processed by Magento’s template engine, allowing attacker-supplied input to be rendered and executed as code.
  • Trigger conditions: no authentication and no user interaction are required to exploit the flaw.
  • Attack vector: network-based (remotely exploitable over HTTP/HTTPS), low attack complexity.
  • Impact: arbitrary code execution in the context of the current user; scope is changed, with high impact to confidentiality, integrity, and availability, indicating potential full compromise of the affected store, including its underlying data and hosting environment.

Affected software

  • Adobe Commerce: versions up to and including 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, and 2.4.4-2026-aug
  • Adobe Commerce B2B: versions up to and including 1.5.3-2026-aug, 1.5.2-2026-aug, 1.4.2-2026-aug, 1.3.4-2026-aug, and 1.3.3-2026-aug
  • Magento Open Source: versions up to and including 2.4.9-2026-aug, 2.4.8-2026-aug, 2.4.7-2026-aug, and 2.4.6-2026-aug

Severity

  • CVSS v3.1 Base Score: 10.0 (CRITICAL)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Apply the hotfix designated for CVE-2026-75650 (referred to in Adobe’s records as "Hotfix for CVE-2026-7565") as published in Adobe Security Bulletin APSB26-146, and update to a build that includes this hotfix as soon as it is available for your version line.
  • If no patch is yet available for your deployment: restrict and closely monitor access to store-facing endpoints that process templated content (including admin, email/notification, and GraphQL-related workflows), watch for unexpected processes or cron entries, and review logs for anomalous template-rendering or failed-notification activity as an indicator of attempted exploitation.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge