Threats / Drupal / CVE-2026-9082
CVE-2026-9082
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Drupal Core vulnerability
Drupal Core contains a SQL injection vulnerability in the database abstraction API that could enable privilege escalation and remote code execution through specially crafted requests.
Verdict
Today item — known-exploited.
SQL injection in Drupal Core's database layer permits attackers to manipulate database queries, potentially escalate privileges and achieve remote code execution. Active exploitation observed in the wild with moderate EPSS score indicates elevated risk despite no CVSS assignment.
CISA KEV Yes · 2026-05-225EPSS 0.88319 (verify live)6Exploit Weaponized · public PoC7CVSS 9.83CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
4 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-05-22).
Probability (EPSS)
EPSS 0.88319 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Drupal, Core. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-89 SQL Injection — weakness family: Injection.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 2 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious request targeting the database abstraction API to inject SQL commands.
Business
Attackers gain unauthorized database access, exposing sensitive user and application data.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I leverage the SQL injection to extract or modify user account records and escalate my privileges to administrator level.
Business
Unauthorized administrative access enables full compromise of the Drupal installation and hosted content.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute arbitrary code on the server through database manipulation or by writing files to the web root.
Business
Complete system compromise allows attackers to deploy malware, steal data, or pivot to internal infrastructure.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by drupalCNA
Credited with finding itMichael Maturi (michaelmaturi)finderBjörn Brala (bbrala)remediation developerBenji Fisher (benjifisher)remediation developercatch (catch)remediation developerLee Rowlands (larowlan)remediation developerDave Long (longwave)remediation developerDrew Webber (mcdruid)remediation developerJess (xjm)remediation developerAnna Kalata (akalata)coordinatorBenji Fisher (benjifisher)coordinatorcatch (catch)coordinatorDamien McKenna (damienmckenna)coordinatorNeil Drumm (drumm)coordinatorGreg Knaddison (greggles)coordinatorHeine Deelstra (heine)coordinatorTim Hestenes Lehnen (hestenet)coordinatorDave Long (longwave)coordinatorDrew Webber (mcdruid)coordinatorJuraj Nemec (poker10)coordinatorPierre Rudloff (prudloff)coordinatorJess (xjm)coordinatorCathy Theys (yesct)coordinator