Critical 10.0 Actively Exploited

Adobe Commerce template RCE, exploited (CVE-2026-75650) [PoC]

CVE-2026-75650

By Yazoul AI · automated

CVE-2026-75650: Adobe Commerce template engine RCE allows unauthenticated code execution (CVSS 10.0). Actively exploited - check for patch APSB26-XX and update now.

Affected: Adobe Commerce Adobe Commerce B2B Adobe Magento

Actively exploited in the wild - CVE-2026-75650 is a critical arbitrary code execution vulnerability in Adobe Commerce versions 2.4.7 and earlier that lets unauthenticated attackers run arbitrary code on the server. Adobe has released a patched version; apply the latest security update immediately.

Overview

CVE-2026-75650 stems from improper neutralization of special elements used in Adobe Commerce’s template engine. An attacker can inject malicious template directives that the server processes, resulting in arbitrary code execution in the context of the current user. The vulnerability requires no user interaction and no privileges, making it remotely exploitable over the network.

The vulnerability carries a CVSS score of 10.0 (Critical). The scope is marked as “changed,” meaning an attacker who compromises the application can pivot to access resources beyond the initial target. CISA has added this CVE to its Known Exploited Vulnerabilities (KEV) catalog, confirming active exploitation in the wild.

While the EPSS model predicts only a 0.7% probability of exploitation in the next 30 days, that statistical likelihood does not account for the confirmed CISA KEV status. Threat actors are already leveraging this bug, so the practical urgency is far higher than the EPSS score suggests.

Affected Systems

Adobe Commerce is the e-commerce platform behind Magento and Adobe Commerce cloud deployments. All versions up to and including 2.4.7 are affected. Administrators running either the on-premises Magento Open Source edition or the Adobe Commerce cloud edition should treat their installations as at risk.

Remediation

Adobe has released security updates addressing CVE-2026-75650. Take the following steps:

  1. Apply the latest Adobe Commerce security patch immediately. Check the Adobe Security Bulletin for your specific version (2.4.7, 2.4.6, or earlier) and upgrade to the patched release.
  2. If you cannot patch immediately, restrict network access to the admin panel and application endpoints as a temporary mitigation.
  3. Review server logs for signs of template injection or unexpected code execution activity.
  4. Monitor for indicators of compromise, as the vulnerability may already be exploited in your environment.

For ongoing coverage of this and related threats, see the latest security news and check breach reports for documented attack campaigns.

Security Insight

Adobe Commerce has become a recurring target for ransomware groups and Magecart-style credit card skimmers, largely because unpatched e-commerce platforms offer direct access to payment data and customer PII. This template engine flaw stands out because it requires no authentication, meaning a single unpatched storefront can be compromised in seconds. The rapid inclusion in CISA’s KEV catalog suggests attackers are weaponizing this faster than typical e-commerce vulnerabilities, reinforcing that patching cadence, not just patch availability, is the difference between a minor incident and a full data breach.

Further Reading

Share:

Never miss a critical vulnerability

Get real-time security alerts delivered to your preferred platform.

Public PoC References

Unverified third-party code

These repositories are publicly listed on GitHub and have not been audited by Yazoul Security. They may contain malware, backdoors, destructive payloads, or operational security risks (telemetry, exfiltration). Treat them as hostile binaries. Inspect source before execution. Run only in isolated, disposable lab environments (offline VM, no credentials, no production data).

Authorized use only. This information is provided for defensive research, detection engineering, and patch validation. Using exploit code against systems you do not own or do not have explicit written permission to test is illegal in most jurisdictions and violates Yazoul's terms of use.

Repository Stars
dinosn/cve-2026-75650-magento-validation-lab

Docker lab for validating the CVE-2026-75650 Magento component-level PHP execution primitive and Adobe VULN-39341 patch.

★ 4
disrex-group/stylesmuggler-adobe-patches

composer require delivery of Adobe's official APSB26-146 (CVE-2026-75650) fix for Magento, via cweagans/composer-patches. Auto-selects the patch for your Magento version.

★ 1
disrex-group/stylesmuggler-adobe-patches-mageos

composer require delivery of Adobe's official APSB26-146 (CVE-2026-75650) fix for Mage-OS stores, via cweagans/composer-patches. Companion to stylesmuggler-adobe-patches (Magento).

★ 0

Showing 3 of 3 known references. Source: nomi-sec/PoC-in-GitHub.

Related Advisories

Never Miss a Critical Alert

CVE advisories, breach reports, and threat intel — delivered daily to your inbox.