Drupal Says a "Highly Critical" Commerce Core Access Bypass Is Under Active Attack — CVE-2026-118539 "May Financially Impact the Vendor"
Drupal Says a "Highly Critical" Commerce Core Access Bypass Is Under Active Attack — CVE-2026-118539 "May Financially Impact the Vendor"
Drupal has warned that threat actors are actively exploiting a "highly critical" security flaw in its Commerce Core component. Tracked as CVE-2026-118539, the vulnerability is a case of missing authorization affecting Commerce Core releases across the module's 2.x and 3.x lines — coverage describes the affected set as versions from 0.0.0 to 2.41 and from 3.0.0 to 3.3.13, with Commerce Core 3.3.13 the fix for 3.x installs and Commerce Core 8.x-2.41 the fix for earlier releases. Drupal acknowledged that the vulnerability is being "actively exploited in the wild," but provided no specifics about the nature of the activity or the extent of the campaign — no indicators of compromise, no attacker profile, just the two fixed versions and the word "now."
The bug is an access bypass, and the advisory language is unusually direct about the consequence. "The module doesn't sufficiently protect certain routes and entity fields, leading to an access bypass that may financially impact the vendor," Drupal wrote, describing a module that "enables you to sell goods and services to customers through an included shopping cart and checkout form or through decoupled applications via APIs." That is a polite way of saying the flaw sits in the money path of an online store: routes and entity fields that Commerce Core fails to sufficiently protect are exactly the surfaces an attacker would touch to view or manipulate what should be vendor-only data — orders, customer details, pricing structures, or store operations reachable through the module's web routes and API endpoints. Researchers Dan Puccetti (dpuccetti), Marcus Johansson (marcus_johansson), and Robert Snyder (rsnyd) are credited with reporting the flaw.
The disclosure lands in the middle of the densest e-commerce exploitation stretch of the year. PolyShell — the Adobe Commerce and Magento upload flaw CISA added to its KEV catalog on October 27 — has already breached hundreds of stores, and we covered that KEV listing last week. The same week brought active exploitation of the Bricksforge WordPress plugin, and October closes with PHP2Shell still being mass-exploited across managed hosting. Drupal Commerce stores were not the direct target of any of those waves — but the pattern around them is: attackers now treat the e-commerce layer, not the server beneath it, as the fastest path to money, and they move from one platform's plugin ecosystem to the next on a weekly rhythm.
For an access-bypass flaw with no CVSS score published and no exploit details shared, the correct severity signal is the one Drupal put in bold: active exploitation, on a commerce component, with fixes that take minutes to apply. Store owners on unsupported or heavily customized Commerce installs have the harder call — the module's history means many stores froze on old versions years ago, and those installations sit inside the affected range no matter what the rest of the Drupal core is doing.
What Should You Do?
- Upgrade Commerce Core immediately — 3.3.13 for the 3.x line, 8.x-2.41 for earlier releases; on a commerce module under active attack, this is not a next-sprint item.
- Audit the routes and entity fields you expose — check which Commerce routes (checkout, order, cart, admin) and entity fields are reachable by anonymous or low-privilege roles; missing-authorization bugs mean your access rules, not Drupal's defaults, are the last line.
- Review store activity for abuse that predates the patch — look for anomalous access to vendor-only data, unexpected order or checkout behavior, and API requests against Commerce endpoints that should have been rejected.
- Check decoupled consumers too — the module explicitly serves "decoupled applications via APIs"; headless storefronts calling Commerce endpoints bypass the theme layer, so verify they authenticate and authorize the same way the monolith would.
The WAF Angle
Access-bypass flaws are the hardest category for any pattern-based defense, because there is no payload to flag — every request is syntactically legitimate, and the violation lives in the answer to a question a WAF cannot ask: should this user be able to reach this route? The attack surface is the same one we described in the PolyShell e-commerce wave — the checkout, cart, and order paths where money moves — except this time the flaw is in the application's own authorization logic rather than an upload endpoint. What actually catches these bugs in production is route-aware controls: rate limits and anomaly detection on commerce endpoints, blocking or challenging unexpected role-based access patterns, and logging that makes "which identity touched which vendor-only route" an answerable question. A WAF that knows your store's legitimate route-and-role matrix turns an invisible bypass into a visible anomaly; one that only inspects payloads for attack syntax will watch this traffic go by and call it clean.