Missing Authorization vulnerability in Drupal Drupal core allows Forceful Browsing. This issue affects Drupal core versions: from 0.0.0 to 10.6.13, from 11.3.0 to 11.3.14, from 11.4.0 to 11.4.4, from 0.0.0 to 11.0.*, from 0.0.0 to 11.1.*, from 0.0.0 to 11.2.*.
CVE-2026-15916
Score 4.2 from GitHub Security Advisory published 2026-08-26. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 4.2; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.2
- EG Score
- 4.2(high)
- EG Risk
- 19(Track)EG Risk 19/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity42% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 2%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 28, 2026
Advisory Details (1)
Auto-updated Aug 26, 2026Drupal core - Moderately critical - Information disclosure - SA-CORE-2026-010 | Drupal.org
https://www.drupal.org/sa-core-2026-010Vendor Advisories for CVE-2026-15916(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Packagist(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| drupal/core | 10.0.0 ... 9.5.9 (493 versions) | 11.3.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 17× in last 7d / 17× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 17:29 UTCEG score recompute
- 2026-08-29 17:29 UTCGHSA enrichment
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-28 15:49 UTCEG score recompute
- 2026-08-28 15:49 UTCGHSA enrichment
- 2026-08-27 18:07 UTCEG score recompute
- 2026-08-27 18:07 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 15:56 UTCGHSA enrichment
- 2026-08-26 15:04 UTCEG score recompute▲ 4.20
- 2026-08-26 15:04 UTCGHSA enrichment
- 2026-08-26 15:01 UTCMITRE cvelistV5CVSS v3 → 4.2 · severity → MEDIUM
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 23:30 UTCNVD update
- 2026-08-25 22:35 UTCEG score recompute
- 2026-08-25 22:34 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
- CVE-2013-3960EG 9.9CRITICAL
- CVE-2015-10143EG 9.8CRITICAL
- CVE-2016-11036EG 9.8CRITICAL
- CVE-2018-11541EG 9.8CRITICAL
- CVE-2011-4183NVD 6.5EG 9.8CRITICAL
- CVE-2018-10251EG 9.8EPSS p90CRITICAL
- CVE-2018-1217EG 9.8EPSS p97CRITICAL
- CVE-2018-0015EG 9.8CRITICAL
- CVE-2017-12582EG 9.8CRITICAL
- CVE-2017-1000056EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-15916?
When was CVE-2026-15916 disclosed?
Is CVE-2026-15916 actively exploited?
What is the CVSS score of CVE-2026-15916?
How do I remediate CVE-2026-15916?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-15916
Is Your Infrastructure Affected by CVE-2026-15916?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.