CVE-2026-19634
MediumCVSS 6.4Summary
PostgreSQL Anonymizer contains a SQL injection vulnerability in two import functions. A user can create a malicious JSON document with specially crafted object names. If a superuser calls anon.import_database_rules() or anon.import_roles_rules(), malicious code is executed with superuser privileges. Fixed in version 3.1.4 and later.
Risk Assessment
An attacker can exploit the vulnerability to execute arbitrary SQL code with superuser privileges, potentially leading to full database compromise.
Recommendation
Upgrade to version 3.1.4 or later and avoid importing untrusted JSON documents.
Other vulnerabilities in PostgreSQL Anonymizer
See all- CVE-2026-83534Medium
PostgreSQL Anonymizer contains a vulnerability in the anon.anonymize_database_parallel() function that allows a table owner to execute arbitrary code with superuser privileges. The issue is fixed in version 3.2.0 and later.
- CVE-2026-19633High
PostgreSQL Anonymizer contains a vulnerability allowing unprivileged masked users to execute arbitrary code by abusing operators, domain casts, or view subqueries carrying untrusted expressions. When evaluated in the masking context, malicious code can run with elevated privileges. Fixed in version 3.1.4 and later.
- CVE-2026-13455Medium
A vulnerability in PostgreSQL Anonymizer allows unprivileged masked users to repeatedly call the anon.hash() function and collect (seed, hash_output) pairs to perform an offline brute-force attack and deduce the salt.
- CVE-2026-11945Medium
PostgreSQL Anonymizer contains a vulnerability that allows a user to gain superuser privileges by creating a JSON document and placing malicious code inside a particular key-value pair. If a superuser calls the import_database_rules() or import_roles_rules() functions, the malicious code is executed with superuser privileges.
Original NVD description (English source)
PostgreSQL Anonymizer contains a SQL injection vulnerability in two import functions. A user can create a malicious JSON document containing specially crafted object names. If a superuser subsequently calls anon.import_database_rules() or anon.import_roles_rules(), the malicious code is executed with superuser privileges. The issue is fixed in PostgreSQL Anonymizer 3.1.4 and later