Threats / Drupal / CVE-2026-9082

CVE-2026-9082 · EUVD no mirror located · GCVE no mirror located Verified 2026-07-06

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-22³EPSS 0.84631 (verify live)⁴Exploit Weaponized · public PoC⁵

Is it exploitable?

— the evidence, ranked above the score

Exploit 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.

vulncheck.com ↗vulncheck.com ↗Confirmed

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.

cisa.gov ↗drupal.org ↗crowdsec.net ↗f5.com ↗Confirmed

Exploited in the wild

Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-05-22).

CISA KEV ↗Confirmed

Probability (EPSS)

EPSS 0.84631 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.

FIRST EPSS ↗High

Severity / affected

Affected: Drupal, Core. Confirm exact fixed builds in the vendor advisory.

NVD ↗Reported

Weakness (CWE)

Mapped to CWE-89 SQL Injection — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.

NVD ↗Reported

WeaknessCWE-89 · SQL InjectionInjection

Who’s exploiting it?

— attribution turns risk into urgency

Attribution 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.

Why it matters

— the attack path, told twice: adversary, then board

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.

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.

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.

What to do

— defensible action

Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.¹

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.

Coverage & confidence

— what we know, and what we don’t

Established (cited)

KEV listing (CISA)

EPSS probability (FIRST)

Weaponized exploit available (VulnCheck)

4 reported-exploitation source(s)

CWE weakness mapping (NVD)

Public exploit availability

Catalogued by drupal (CNA)

Named finder/reporter credit (CVE.org)

Coverage gaps — stated, not hidden

No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.

EPSS & exposure are time-varying; verify live at the source.

Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.

Disclosure & credit²

Catalogued by drupalCNA