CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →
← Back to Daily brief 2026-05-20
CRITICALCVE-2026-9082exploitedupdatedNATOA1vulnerability

CVE-2026-9082: anonymous SQL injection in Drupal core on PostgreSQL, Highly critical, exploited and CISA KEV-listed

Drupal core CVE-2026-9082: anonymous SQL injection on PostgreSQL sites, exploited in the wild from 2026-05-22

Analysis

The Drupal Security Team pre-announced a Highly critical core release on 2026-05-18, scored 20 of 25 (AC:None, A:None, E:Theoretical, TD:Uncommon), and urged administrators to reserve the 2026-05-20 window from 17:00 to 21:00 UTC because "exploits might be developed within hours or days" (Drupal PSA-2026-05-18). SA-CORE-2026-004 followed on 2026-05-20 with CVE-2026-9082: a flaw in core's database abstraction API lets an anonymous attacker send specially crafted requests that result in arbitrary SQL injection on sites using PostgreSQL, which can lead to information disclosure and in some cases privilege escalation, remote code execution or other attacks (Drupal SA-CORE-2026-004). Searchlight Cyber traced it to the PostgreSQL entity-query override of the case-insensitive IN operator, which builds SQL placeholder names from the keys of the submitted value array, so attacker-chosen JSON object keys reach the SQL text through two anonymous entry points, the JSON login endpoint and the JSON:API filter syntax (Searchlight Cyber, 2026-05-21). The fixed releases are 11.3.10, 11.2.12, 11.1.10, 10.6.9, 10.5.10 and 10.4.10, and Drupal 9 and 8.9 sites are told to try applying a best-effort patch file by hand (Drupal SA-CORE-2026-004); Drupal 7 is not affected (Drupal PSA-2026-05-18). On 2026-05-22 Drupal raised the risk score to 23 of 25 because exploit attempts were being detected in the wild (Drupal SA-CORE-2026-004), and CISA added the flaw to its Known Exploited Vulnerabilities catalog the same day (CISA KEV catalog, 2026-05-22); the Drupal CNA scores it CVSS 9.8 (ENISA EUVD-2026-31153). By 2026-05-21 Imperva had observed over 15,000 attack attempts against almost 6,000 sites in 65 countries, most of it probing (Imperva, 2026-05-21).

Triage: most of this traffic is automated probing that tests whether a site is vulnerable (Imperva, 2026-05-21); a probe against a MySQL or SQLite site, or one already on a fixed release, is noise, while the same request against an unpatched PostgreSQL site is an attempt that calls for the account review above (Drupal SA-CORE-2026-004).

Cited evidence

exploits might be developed within hours or days.

This issue is being protected by Drupal Steward.

Drupal Security Team (PSA-2026-05-18) 2026-05-18

A vulnerability in this API allows an attacker to send specially crafted requests, resulting in arbitrary SQL injection for sites using PostgreSQL databases.

The risk score has been updated to reflect that exploit attempts are now being detected in the wild.

Drupal Security Team (SA-CORE-2026-004) 2026-05-20

Since CVE-2026-9082 was released, Imperva has observed over 15,000 attack attempts targeting almost 6,000 individual sites across 65 countries.

Most of the observed activity so far appears to be probing.

Imperva 2026-05-21

There are two anonymous entry points that we have confirmed reach this loop with attacker-controlled array keys: the JSON login endpoint and the JSON:API filter syntax.

Searchlight Cyber 2026-05-21

Updates3

Update

Drupal published SA-CORE-2026-004 on 2026-05-20 with CVE-2026-9082: a vulnerability in core's database abstraction API allows an attacker to send specially crafted requests resulting in arbitrary SQL injection for sites using PostgreSQL, it can be exploited by anonymous users, and it "can lead to information disclosure, and in some cases privilege escalation, remote code execution, or other attacks" (Drupal SA-CORE-2026-004). The pre-announcement had scored it 20 of 25 and warned that "exploits might be developed within hours or days" (Drupal PSA-2026-05-18).

Affected versions run from 8.9.0 up to (not including) 10.4.10, 10.5.0 before 10.5.10, 10.6.0 before 10.6.9, 11.0.0 before 11.1.10, 11.2.0 before 11.2.12 and 11.3.0 before 11.3.10, and the fixed releases are 10.4.10, 10.5.10, 10.6.9, 11.1.10, 11.2.12 and 11.3.10; Drupal 9 and 8.9 sites get best-effort patch files to apply manually (Drupal SA-CORE-2026-004), and Drupal 7 is not affected (Drupal PSA-2026-05-18). Sites using the Drupal Steward web application firewall are already protected from known attack vectors but should upgrade in the near future (CSO Online, 2026-05-20). NCSC.ch had carried the pre-announcement on 2026-05-19 (NCSC.ch Security Hub).

Update

On 2026-05-22 Drupal updated SA-CORE-2026-004, raising the risk score to 23 of 25 because exploit attempts are now being detected in the wild (Drupal SA-CORE-2026-004); NCSC.ch marked Security Hub post 12584 as actively exploited the same day (NCSC.ch Security Hub), and CISA added CVE-2026-9082 to its Known Exploited Vulnerabilities catalog on 2026-05-22 (CISA KEV catalog, 2026-05-22).

Imperva observed over 15,000 attack attempts targeting almost 6,000 sites across 65 countries, most of it probing of JSON:API routes, with Gaming and Financial Services sites drawing almost half the attacks (Imperva, 2026-05-21). Searchlight Cyber's analysis shows attacker-controlled array keys, sent as JSON object keys to the anonymous JSON login endpoint or through the JSON:API filter syntax, reaching the placeholder names that the PostgreSQL entity-query override builds for the case-insensitive IN operator (Searchlight Cyber, 2026-05-21).

Correction

A score of 20 of 25 is Drupal's top tier, Highly critical, which covers 20 to 25, not the second-highest (Drupal security risk levels); it stayed below 25 because no exploit existed yet and only uncommon configurations were affected (The Register, 2026-05-19), and on 2026-05-22 it rose to 23 of 25 with exploitation detected (Drupal SA-CORE-2026-004). A mitigation did exist before the patch: the PSA said the issue was protected by Drupal Steward (Drupal PSA-2026-05-18). Only Drupal 9 and 8.9 sites were left with patch files to apply by hand; the end-of-life 11.1.x and 10.4.x lines received full releases, 11.1.10 and 10.4.10 (Drupal SA-CORE-2026-004).

The Drupal CNA scores CVE-2026-9082 CVSS 9.8 (ENISA EUVD-2026-31153); 6.5 is NIST's score (BleepingComputer, 2026-05-22). Moving a site off PostgreSQL is not a control any source offers; the sourced interim measure is Drupal Steward. Imperva's figures count attack attempts, mostly probing, aimed chiefly at Gaming and Financial Services sites (Imperva, 2026-05-21). No source names Swiss, EU or university Drupal sites as targets or says Drupal dominates Swiss public portals; the Federal Administration's standard web platform is based on Livingdocs (Swiss Federal Chancellery).

Sources15

Revision history

  1. Published 2026-05-20-a0f7b07f
  2. Update 2026-05-21-77cdc4cd

    Drupal patches "highly critical" pre-auth SQL injection (CVE-2026-9082) on PostgreSQL-backed installs of Drupal 8.9–11.3; the Security Team warned that "exploits might be developed within hours or days" of advisory release. EU/CH government portals and university CMSes are the primary exposed surface (Drupal Security Team, 2026-05-20; NCSC-CH, 2026-05-19).

    Changed: cves priority sectors sources tags body

  3. Update 2026-05-23-852c21c8

    Drupal CVE-2026-9082 now actively exploited; CISA KEV-listed 2026-05-22. Drupal updated SA-CORE-2026-004 to confirm in-the-wild exploit attempts on PostgreSQL-backed sites; Imperva measured 15,000+ attempts against ~6,000 sites across 65 countries; NCSC.ch Security Hub flipped post 12584 to "Actively exploited" the same day (Drupal Security Team, 2026-05-22 · Imperva, 2026-05-21 · NCSC-CH, 2026-05-22).

    Changed: actions cves evidence immediate_action priority sources tags body

  4. Correction 2026-10-21T1148Z-audit

    Drupal's 20 of 25 is its top tier, Highly critical, and rose to 23 of 25 on 2026-05-22; Drupal Steward protected sites before the patch, only Drupal 9 and 8.9 needed manual patch files, and the CNA scores CVE-2026-9082 CVSS 9.8 rather than 6.5. Switching databases is not a sourced control, Imperva's figures are attack attempts that were mostly probing, and no source names Swiss, EU or university Drupal sites as targets.

    Changed: actions affected_products body classification cves evidence headline immediate_action kind regions sectors sources sourcing_note summary tags techniques title

PROVENANCE

AI-generated · no human review · this permalink is the shareable record for the finding · verify operationally critical claims against the linked primary source.