Quick answers
- Is CVE-2026-19634 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-19634 being exploited in the wild.
- How severe is CVE-2026-19634?
- Medium severity, with a CVSS score of 6.4, published 6 September 2026.
- Which products and versions are affected?
- Dalibo PostgreSQL Anonymizer before 3.1.4.
- Is there a fix for CVE-2026-19634?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-19634 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-19634?
- Check whether you run Dalibo PostgreSQL Anonymizer at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
PostgreSQL Anonymizer versions prior to 3.1.4 contain a SQL injection vulnerability in the to_seclabel() function, which fails to properly escape object names when interpolating them into SQL statements. An attacker can craft a JSON document with specially crafted object names containing SQL comments (--) to comment out security tokens added in version 3.1.1, breaking the previous fix. When a superuser calls anon.import_database_rules() or anon.import_roles_rules() on the malicious JSON, the injected SQL executes with superuser privileges, allowing privilege escalation. The vulnerability requires social engineering or access to influence the rules file that a superuser imports, but no direct superuser privileges. The fix is available in PostgreSQL Anonymizer 3.1.4 and later.
Affected products
- Dalibo PostgreSQL Anonymizer before 3.1.4
Timeline
- 2026-09-06: disclosed