What it is
CVE-2026-118539 is an unauthenticated Commerce Core - Highly critical - Access bypass - SA-CONTRIB-2026-254. Missing Authorization vulnerability in Drupal Commerce Core allows Forceful Browsing. This issue affects...
Vulnerability report
Commerce Core - Highly critical - Access bypass - SA-CONTRIB-2026-254
Drupal / Commerce Core · affected before 2.41
Decision summary
Direct answers before the deeper technical record.
What it is
CVE-2026-118539 is an unauthenticated Commerce Core - Highly critical - Access bypass - SA-CONTRIB-2026-254. Missing Authorization vulnerability in Drupal Commerce Core allows Forceful Browsing. This issue affects...
Have exploitation attempts been observed?
Yes. Exploitation attempts have been reported for this vulnerability. Previdian lists it as a known exploited vulnerability. Also reported by third-party sources. Confidence is high.
Who is affected?
Drupal / Commerce Core affected before 2.41.
What should we do?
Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.
Overview
Missing Authorization vulnerability in Drupal Commerce Core allows Forceful Browsing. This issue affects Commerce Core versions: from 0.0.0 to 2.41, from 3.0.0 to 3.3.13.
Exploitation evidence
Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.
Drupal Contrib
A trusted third party reported exploitation attempts.
Per-source evidence links for KEV attestations are available through the Previdian Pro API.
Learn about Pro API access| Source | Added |
|---|---|
| Drupal Contrib First | 2026-10-28 17:11 UTC |
| The Hacker News | 2026-10-30 08:33 UTC |
Detection
Make the evidence actionable in scanner, SOC, and edge-control workflows.
No scanner integrations recorded yet.
No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.
Learn about virtual patches →No detection artifacts or sensor request patterns are available for this CVE yet.
Check back as sensor telemetry and scanner integrations are updated.
Risk and context
CVSS v3.1
Potential damage if exploited. Separate from whether attackers are using it.
Previdian estimate — not a CNA or NVD score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
—
Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.
Recent mention · The Hacker News
Ravie LakshmananOct 30, 2026Vulnerability / Web Security Drupal has warned that threat actors are exploiting a "highly critical" security flaw in its Commerce Core component. The vulnerability, tracked as CVE-2026-118539 (CVSS score: N/A), is a case of missing authorization...
Read full advisoryRecent mention · The Hacker News
Hackers Actively Exploit Highly Critical Drupal Commerce Core Authorization Bypass FlawThe Hacker News · 30 Oct 2026
Ravie LakshmananOct 30, 2026Vulnerability / Web Security Drupal has warned that threat actors are exploiting a "highly critical" security flaw in its Commerce Core component. The vulnerability, tracked as CVE-2026-118539 (CVSS score: N/A), is a case of missing authorization affecting Commerce Core versions from 0.0.0 to 2.41 and from 3.0.0 to 3.3.13. "This module enables you to sell goods and services to customers through an included shopping cart and checkout form or through decoupled applications via APIs," Drupal said in an advisory. "The module doesn't sufficiently protect certain...
Timeline
08:33 UTC
Exploitation attempts reported by an external source
03:09 UTC
Vulnerability disclosed publicly
17:11 UTC
High-confidence, third-party report of exploitation attempts
15:50 UTC
Identifier reserved by the CNA
Pro API
Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.
GET /api/v2/pro/kevs/CVE-2026-118539
Sample API response{
"cve_id": "CVE-2026-118539",
"confidence": "High",
"cvss_score": 9.8,
"cvss_estimated": true,
"epss_score": null,
"exploit_status": {
"exploited_in_the_wild": true,
"active_exploitation_observed": false
},
"sensor_telemetry": { "attempts": 0, "sensors": 0 }
}