Analyst readout for executives and security teams
Plain-English summary
A database user with table-creation rights can set a malicious column name that runs when a superuser later uses PostgreSQL Anonymizer's k-anonymity function. Successful abuse could give that code superuser-level database privileges. The issue is fixed in PostgreSQL Anonymizer 3.1.0 and later.
Executive priority
Prioritize remediation on databases where less-trusted users can create tables and anonymization tasks run with superuser privileges. For tightly controlled databases, urgency is lower but upgrade and permission review should still be scheduled promptly.
Technical view
CVE-2026-9617 is SQL injection in PostgreSQL Anonymizer's anon.k_anonymity() handling of column identifiers. If a privileged caller runs the function against attacker-controlled table metadata, code in a column identifier can execute with superuser privileges. Risk is higher on PostgreSQL 14 or upgraded instances where public schema CREATE may still be allowed.
Likely exposure
Exposure is limited to PostgreSQL environments using PostgreSQL Anonymizer where untrusted or lower-privileged users can create tables and a superuser runs anon.k_anonymity(). PostgreSQL 15+ defaults reduce exposure unless CREATE TABLE was explicitly granted.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. Abuse requires high privileges to create relevant database objects and user interaction through a superuser invoking the vulnerable function, but impact is high if conditions align.
Researcher notes
Affected-version evidence in the bundle is limited beyond the statement that 3.1.0 and later resolve the issue. Focus validation on extension version, PostgreSQL major-version history, schema CREATE grants, and whether superusers run anon.k_anonymity() against attacker-influenced database objects.
Mitigation direction
- Upgrade PostgreSQL Anonymizer to 3.1.0 or later.
- Review vendor guidance for any additional configuration recommendations.
- Restrict CREATE privileges on public and sensitive schemas.
- Limit who can invoke anon.k_anonymity() as a privileged role.
- Review upgraded PostgreSQL 14-era instances for inherited public schema permissions.
Validation and detection
- Inventory PostgreSQL instances using PostgreSQL Anonymizer.
- Confirm installed PostgreSQL Anonymizer version is 3.1.0 or later.
- Review schema CREATE grants, especially on public schemas.
- Identify users able to create tables in anonymized databases.
- Review privileged anonymization jobs using anon.k_anonymity().
- Check audit logs for unusual table or column identifiers before privileged runs.
Public sources used
Based on public source material and reviewed before publication.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-9617 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H 0.9 5.9 PostgreSQL Vulnerability scoring details
Base CVSS 3.1 score
6.8 MediumVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reserved CVE Program
The CVE ID was reserved by the assigning CNA.
- CVE published CVE Program
The CVE record was published.
- CVE updated CVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 source CVE List V5
- https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/640 CVE reference, PostgreSQL
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.