CVE-2026-9082
CRITICALCVE-2026-9082 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in drupal/core. It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-05-22) — treat it as actively exploited and patch now. O3 Security confirms whether CVE-2026-9082 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Drupal core - Highly critical - SQL injection - SA-CORE-2026-004
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2026-05-22. Federal agencies were required to remediate by 2026-05-27.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2026-9082.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2026-9082 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE sits: patch-first territory.
Where this sits among everything scored
Of 0 CVEs with a current EPSS score, this one falls in the 50–90% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
drupal/core🐘drupal/core🐘drupal/core🐘drupal/core🐘drupal/core🐘drupal/coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | drupal/core | ≥ 8.9.0&&< 10.4.10 | 10.4.10 |
| 🐘Packagist | drupal/core | ≥ 10.5.0&&< 10.5.10 | 10.5.10 |
| 🐘Packagist | drupal/core | ≥ 10.6.0&&< 10.6.9 | 10.6.9 |
| 🐘Packagist | drupal/core | ≥ 11.0.0&&< 11.1.10 | 11.1.10 |
| 🐘Packagist | drupal/core | ≥ 11.2.0&&< 11.2.12 | 11.2.12 |
| 🐘Packagist | drupal/core | ≥ 11.3.0&&< 11.3.10 | 11.3.10 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Drupal Core 10.5.5 - Error-Based SQL Injection
by cardosource · Jun 1, 2026
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update drupal/core to 10.4.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-9082 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-9082 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-9082. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-9082 in your dependencies?
O3 detects CVE-2026-9082 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.