What products are affected by CVE-2026-9082?

CVE-2026-9082 affects Drupal Core. Refer to the vendor advisory and NVD record for affected versions.

Is there a public exploit for CVE-2026-9082?

Yes. Public exploit code or proof-of-concept has been identified for CVE-2026-9082. This lowers the barrier for exploitation and increases the urgency of patching. Organizations should prioritize remediation immediately.

What is the EPSS score for CVE-2026-9082?

CVE-2026-9082 has an EPSS score of 10.4%, placing it in the 93th percentile. This means it has a 10.4% probability of being exploited in the next 30 days, higher than 93% of all known vulnerabilities. EPSS (Exploit Prediction Scoring System) is maintained by FIRST and uses real-world threat data to estimate exploitation likelihood.

Actively Exploited — CISA KEV

CVE-2026-9082: Drupal Core Critical Vulnerability

Severity: Critical | CVSS 3.1: 9.8 | Published: 2026-05-20 | KEV Added: 2026-05-22

What is CVE-2026-9082?

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Drupal Drupal core allows SQL Injection. This issue affects Drupal core: from 8.9.0 before 10.4.10, from 10.5.0 before 10.5.10, from 10.6.0 before 10.6.9, from 11.0.0 before 11.1.10, from 11.2.0 before 11.2.12, from 11.3.0 before 11.3.10.

Technical Analysis

Weakness Classification

This vulnerability is classified as CWE-89 — SQL Injection. Untrusted data is included in SQL queries without proper sanitization, allowing attackers to read, modify, or delete database contents.

Attack Vector Breakdown

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Impact Analysis

This vulnerability is exploitable over the network, meaning any system reachable via the internet or internal network is potentially at risk without physical access. The attack complexity is low, requires no special privileges, and needs no user interaction — making it straightforward to exploit at scale. Successful exploitation can result in full confidentiality breach (complete data disclosure), complete integrity compromise (data modification or code execution), total availability loss (denial of service). Untrusted data is included in SQL queries without proper sanitization, allowing attackers to read, modify, or delete database contents.

Exploitation Probability (EPSS): 10.4% chance of exploitation in the next 30 days (93th percentile). This is a significantly elevated exploitation probability — prioritize patching.

Exploit Availability

Public exploit code or proof-of-concept is available for CVE-2026-9082. This significantly increases the risk of exploitation, as attackers can use or adapt existing exploit code rather than developing their own. A public exploit reference has been identified. Organizations should treat this as an urgent patching priority.

Is CVE-2026-9082 being exploited?

Yes. CVE-2026-9082 is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, restricted to CVEs with confirmed active exploitation in the wild. CISA added this vulnerability on 2026-05-22. Inclusion in KEV triggers the patching mandate under BOD 22-01 for U.S. federal civilian agencies, with a remediation deadline of 2026-05-27. Additionally, public exploit code is available, which lowers the barrier for attackers.

How to fix CVE-2026-9082

Apply the security update issued by Drupal for Core. Check the Drupal Security Advisories page for the specific patch or update. If an immediate patch is not possible, consult the vendor advisory for mitigation guidance, restrict network exposure of the affected service, and monitor logs for indicators of exploitation. CISA's Known Exploited Vulnerabilities catalog requires U.S. federal agencies to remediate this vulnerability by the due date shown below under Binding Operational Directive 22-01. Private organizations should treat KEV entries as priority-one patches because active exploitation has been confirmed in the wild.

Related Vulnerabilities

Other actively exploited vulnerabilities sharing the same weakness pattern (CWE-89 — SQL Injection):

CVE-2026-42208 (Critical 9.8) [same CWE] — LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native)…
CVE-2026-21643 (Critical 9.8) [same CWE] — An improper neutralization of special elements used in an sql command ('sql…
CVE-2024-43468 (Critical 9.8) [same CWE] — Microsoft Configuration Manager Remote Code Execution Vulnerability
CVE-2025-25257 (Critical 9.8) [same CWE] — An improper neutralization of special elements used in an SQL command ('SQL…

Frequently asked questions

Is CVE-2026-9082 critical?

CVE-2026-9082 has a CVSS 3.1 base score of 9.8 — Critical severity. It should be treated as a priority patch, especially given the active exploitation confirmed by CISA. The availability of public exploit code further increases the urgency.

Is CVE-2026-9082 being actively exploited?

Yes — CISA added CVE-2026-9082 to the Known Exploited Vulnerabilities catalog on 2026-05-22. Inclusion in KEV means CISA has confirmed in-the-wild exploitation. Public exploit code has also been identified, making exploitation accessible to a broader range of threat actors.

How do I patch CVE-2026-9082?

Apply the security update from Drupal for Core. Federal agencies must remediate by 2026-05-27 under BOD 22-01. Refer to the Drupal Security Advisories for the official patch.

What type of vulnerability is CVE-2026-9082?

CVE-2026-9082 is classified under CWE-89 (SQL Injection). Untrusted data is included in SQL queries without proper sanitization, allowing attackers to read, modify, or delete database contents.

What is the CVSS score for CVE-2026-9082?

CVE-2026-9082 has a CVSS 3.1 base score of 9.8, classifying it as Critical severity. The attack vector is Network, attack complexity is Low, and no privileges are required.