# Drupal Core has a SQL Injection issue Advisory record · `GHSA-ghwc-95x2-682j` - **Identifiers:** `GHSA-ghwc-95x2-682j` · `BIT-drupal-2026-9082` · `CVE-2026-9082` · `DRUPAL-CORE-2026-004` · `PKSA-h76q-q9b2-4kdc` - **State:** Confirmed - **Severity:** CVSS 9.8 Critical - **Critical:** Yes: KEV, CVSS 9+, CVSS 7+ and EPSS - **Weakness (CWE):** [CWE-89](https://cwe.mitre.org/data/definitions/89.html) - **Tags:** [SQL injection](https://agentprime.io/advisories/tag/sql-injection.md) - **Published:** 20 May 2026 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 20 May 2026, 21:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Critical Critical, because: - In CISA’s KEV catalogue since 22 May 2026: it is known to be exploited. - CVSS score 9.8: 9.0 or more. - CVSS score 9.8 (7.0 or more) and EPSS 0.89 (0.1 or more): a high score and a real chance of exploitation in the next 30 days. How we decide what’s critical: ## Affected packages - `drupal/core` (Packagist): affected `>=8.9.0, <10.4.10 || >=10.5.0, <10.5.10 || >=10.6.0, <10.6.9 || >=11.0.0, <11.1.10 || >=11.2.0, <11.2.12 || >=11.3.0, <11.3.10`; fixed in `10.4.10`, `10.5.10`, `10.6.9`, `11.1.10`, `11.2.12`, `11.3.10` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > The Packagist package drupal/core is affected in versions 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, and from 11.3.0 before 11.3.10. The source describes an SQL injection flaw but gives few details about the conditions needed to exploit it or its impact. Upgrade drupal/core to 10.4.10, 10.5.10, 10.6.9, 11.1.10, 11.2.12, or 11.3.10, depending on the release line in use. Written 31 Oct 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 9.8 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, from CNA (drupal) - **CISA KEV:** Listed since 22 May 2026: known to be exploited. - **EPSS:** 0.89, the 99th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 13:58 UTC: First seen by agentprime - 31 Oct 2026, 13:58 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-ghwc-95x2-682j) ## Sources - [GitHub Advisory Database: GHSA-ghwc-95x2-682j](https://github.com/advisories/GHSA-ghwc-95x2-682j) - [OSV: GHSA-ghwc-95x2-682j](https://osv.dev/vulnerability/GHSA-ghwc-95x2-682j) - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .