CVE-2026-118539: Authorization Bypass in Drupal Commerce Core
CVE-2026-118539 is a missing-authorization vulnerability in Drupal Commerce Core, the contributed module providing shopping carts, checkout workflows, and commerce APIs. Insufficient protection of certain application routes and entity fields allows unauthenticated attackers to bypass access controls through forceful browsing and access or modify commerce data without appropriate permissions. Both traditional and headless deployments are affected. Affected releases precede Commerce Core 8.x-2.41 in the 2.x branch and include 3.x releases before 3.3.13. Drupal classified the vulnerability as highly critical, with a Drupal security risk score of 21/25, and confirmed active exploitation.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can compromise the confidentiality and integrity of commerce information and cause financial losses for merchants. Potential consequences include exposure of private information, unauthorized changes to orders or other commerce data, and circumvention of payment-related workflows. Fraudulent order attempts have been observed, but the extent of exploitation is not established. Remote code execution and full website takeover are not established consequences of this vulnerability.
Mitigation
If you can’t patch tonight, do this now.
Where JSON:API write operations are unnecessary, restrict that interface to read-only access to reduce an available attack surface; this is not a complete workaround for all affected routes. Verify actual payment receipt before fulfilling orders. Review historical transactions for orders without corresponding payments or orders marked paid without payment records, and correlate suspicious changes with website access logs. These measures supplement rather than replace immediate upgrading.
Remediation
Patch, then assume compromise.
Upgrade Drupal Commerce Core to 8.x-2.41 or a later supported security release on the 2.x branch, or to 3.3.13 or a later supported security release on the 3.x branch. These are Commerce module updates; updating Drupal core alone does not remediate the vulnerability. After patching, retrospectively audit orders and reconcile their payment states against actual payment-provider transactions, investigating unexplained pricing, discounts, fees, adjustments, and missing payments.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Frequently asked questions
- Is CVE-2026-118539 exploited in the wild?
- Yes. As of Nov 6, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2026-118539?
- As of Nov 6, 2026, Mallory has found no public exploit for CVE-2026-118539.
- Is there a patch for CVE-2026-118539?
- Upgrade Drupal Commerce Core to 8.x-2.41 or a later supported security release on the 2.x branch, or to 3.3.13 or a later supported security release on the 3.x branch. These are Commerce module updates; updating Drupal core alone does not remediate the vulnerability.
- How severe is CVE-2026-118539?
- CVE-2026-118539 has a CVSS v3.1 score of 6.5 (Medium) and an EPSS score of 0.67% (53rd percentile) as of Nov 6, 2026.
Recent activity
74 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.