CVE-2026-9617: PostgreSQL Anonymizer: malicious column name allows SQL injection via anon.k_anonymity() function

Published May 27, 2026
·
Updated

PostgreSQL Anonymizer contains a vulnerability that allows a user to gain superuser privileges by creating a table and placing malicious code inside a column identifier. If a superuser calls the k-anonymity function, the malicious code is executed with superuser privileges. The risk is higher with PostgreSQL 14 or with instances upgraded from PostgreSQL 14 or a prior version. With PostgreSQL 15 and later, the creation permission on the public schema is revoked by default and this exploit can only be achieved by a user who was explicitly granted the CREATE TABLE privilege. The problem is resolved in PostgreSQL Anonymizer 3.1.0 and further versions

Affected Software

2 affected components
PostgreSQL Anonymizer PostgreSQL Anonymizer<3.1.0
Dalibo Anonymizer Postgresql=2.5.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade PostgreSQL Anonymizer to a version that resolves this vulnerability.

    Fixed in 3.1.0
  2. Compensating control

    For PostgreSQL 14 and instances upgraded from PostgreSQL 14 or a prior version, ensure only trusted users are explicitly granted the CREATE TABLE privilege on the public schema, since the described exploit requires that privilege.

Event History

May 27, 2026
CVE Published
via MITRE·01:55 PM
Data Sourced
via MITRE·01:55 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:17 PM
DescriptionSeverityWeaknessAffected Software
Apr 28, 58520
Event
via FIRST·06:42 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-9617?

The severity of CVE-2026-9617 is classified as medium with a score of 6.8.

2

How do I fix CVE-2026-9617?

To fix CVE-2026-9617, avoid using untrusted inputs as column identifiers in the anon.k_anonymity() function.

3

What type of attack does CVE-2026-9617 facilitate?

CVE-2026-9617 facilitates an SQL injection attack that can lead to superuser privilege escalation.

4

What is affected by CVE-2026-9617?

CVE-2026-9617 affects the PostgreSQL Anonymizer when the k-anonymity function is used with malicious column names.

5

When was CVE-2026-9617 published?

CVE-2026-9617 was published on May 27, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203