CVE-2026-9617: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in DALIBO PostgreSQL Anonymizer
CVE-2026-9617 is a SQL injection vulnerability in the DALIBO PostgreSQL Anonymizer that allows a user to escalate privileges to superuser by injecting malicious code into a column identifier when creating a table. Execution of this code occurs if a superuser calls the k-anonymity function. The risk is higher on PostgreSQL 14 or instances upgraded from that version, while PostgreSQL 15 and later reduce risk by revoking public schema creation permissions by default. The vulnerability is fixed in PostgreSQL Anonymizer version 3.1.0 and later.
AI Analysis
Technical Summary
The DALIBO PostgreSQL Anonymizer contains an SQL injection vulnerability where a user with CREATE TABLE privileges can embed malicious code in a column identifier. When a superuser invokes the k-anonymity function, this code executes with superuser privileges, leading to privilege escalation. PostgreSQL 14 and earlier or upgraded instances are more vulnerable due to default permissions. PostgreSQL 15+ mitigates risk by revoking CREATE TABLE permission on the public schema by default, limiting exploitability to users explicitly granted this privilege. The issue is resolved in PostgreSQL Anonymizer 3.1.0 and subsequent releases.
Potential Impact
Successful exploitation allows privilege escalation to superuser level via SQL injection, resulting in full control over the database instance. This can compromise confidentiality, integrity, and availability of the database. The impact is rated medium with a CVSS score of 6.8. The vulnerability is more easily exploited on PostgreSQL 14 or upgraded instances due to default permissions. PostgreSQL 15 and later reduce the attack surface by restricting schema creation permissions.
Mitigation Recommendations
Upgrade to PostgreSQL Anonymizer version 3.1.0 or later, where this vulnerability is fixed. For PostgreSQL 15 and later, the default revocation of CREATE TABLE permission on the public schema reduces risk, but users should ensure that only trusted users have CREATE TABLE privileges. Patch status is not explicitly stated beyond the fixed version; therefore, verify with the vendor advisory for the latest remediation guidance.
CVE-2026-9617: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in DALIBO PostgreSQL Anonymizer
Description
CVE-2026-9617 is a SQL injection vulnerability in the DALIBO PostgreSQL Anonymizer that allows a user to escalate privileges to superuser by injecting malicious code into a column identifier when creating a table. Execution of this code occurs if a superuser calls the k-anonymity function. The risk is higher on PostgreSQL 14 or instances upgraded from that version, while PostgreSQL 15 and later reduce risk by revoking public schema creation permissions by default. The vulnerability is fixed in PostgreSQL Anonymizer version 3.1.0 and later.
CVSS v3.1
Score 6.8medium
Affected software
pkg:github/dalibo/postgresql_anonymizerRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The DALIBO PostgreSQL Anonymizer contains an SQL injection vulnerability where a user with CREATE TABLE privileges can embed malicious code in a column identifier. When a superuser invokes the k-anonymity function, this code executes with superuser privileges, leading to privilege escalation. PostgreSQL 14 and earlier or upgraded instances are more vulnerable due to default permissions. PostgreSQL 15+ mitigates risk by revoking CREATE TABLE permission on the public schema by default, limiting exploitability to users explicitly granted this privilege. The issue is resolved in PostgreSQL Anonymizer 3.1.0 and subsequent releases.
Potential Impact
Successful exploitation allows privilege escalation to superuser level via SQL injection, resulting in full control over the database instance. This can compromise confidentiality, integrity, and availability of the database. The impact is rated medium with a CVSS score of 6.8. The vulnerability is more easily exploited on PostgreSQL 14 or upgraded instances due to default permissions. PostgreSQL 15 and later reduce the attack surface by restricting schema creation permissions.
Mitigation Recommendations
Upgrade to PostgreSQL Anonymizer version 3.1.0 or later, where this vulnerability is fixed. For PostgreSQL 15 and later, the default revocation of CREATE TABLE permission on the public schema reduces risk, but users should ensure that only trusted users have CREATE TABLE privileges. Patch status is not explicitly stated beyond the fixed version; therefore, verify with the vendor advisory for the latest remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- PostgreSQL
- Date Reserved
- 2026-05-26T16:36:40.963Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a16f9eae29bf47b50c0f5be
Added to database: 05/27/2026, 14:04:26 UTC
Last enriched: 06/03/2026, 20:57:13 UTC
Last updated: 07/31/2026, 19:23:00 UTC
Views: 70
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.