Skip to main content
Mallory
MediumVulnerability

CVE-2026-118539: Authorization Bypass in Drupal Commerce Core

Published Oct 30, 2026 · Updated 11 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days74 mentions · peak 32 in a dayToday
CVSS6.5Medium · v3.1
EPSS0.67%53rd percentile
CISA KEVNoNot listed
In the wildReported19 exploitation records in Mallory
IdentifiersCVE-2026-118539CWE-862 · Missing Authorization

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

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.
Activity feed

Recent activity

74 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
malware newsNews · Nov 6, 2026October 2026 CVE Landscape - Malware Analysis - Malware Analysis, News and IndicatorsA Drupal Commerce Core vulnerability reported as actively exploited in October 2026.Read more ↗csirt italiaNews · Nov 5, 2026Drupal: rilevato sfruttamento in rete della CVE-2026-118539 - ACNA missing-authorization vulnerability in Drupal Commerce Core affecting security controls on specific routes and application entity fields. Attackers can bypass authorization checks and access sensitive information. The report assigns a CVSS v3.1 score of 6.5 and states that active exploitation has been detected. Affected releases are versions before 2.41 and 3.x versions before 3.3.13; the vendor has issued fixes and recommends prompt upgrades.Read more ↗nuclei templates pull requestsNews · Nov 3, 2026Drupal Commerce Core - Anonymous Guest Cart Admin Access Bypass (CVE-2026-118539) by alex700 · Pull Request #17656 · projectdiscovery/nuclei-templatesAn order administration route access-bypass vulnerability in Drupal Commerce Core. The content references a detector template and proof-of-concept reproduction using an anonymous guest cart against an order state-transition route. It does not establish affected versions or exploitation in the wild.Read more ↗the hacker newsNews · Nov 2, 2026⚡ Weekly Recap: Critical CVEs, Linux DDoS Botnet, Device-Code Phishing, Android Spyware and MoreListed vulnerability affecting Drupal; technical details are not provided.Read more ↗
+14 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity54Community discussion across Reddit, Mastodon, and other social sources.