CVE-2026-105618EUVD-2026-112290GHSA-GXMR-V93G-WPQ2
PostgreSQL Anonymizer: Masked partitions and child tables are not masked when they are queried through their parent
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.3.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
PostgreSQL Anonymizer, an extension used to mask personal data in PostgreSQL databases, is affected when masking rules are applied to partitioned or inherited tables. Data is correctly masked when those child tables are queried directly, but querying through the parent table returns unmasked data, exposing sensitive information.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
PostgreSQL Anonymizer's documentation recommends applying rules on partitions and inheritance tables. Direct access to the paritions / inheritance tables is masked but not thru the parent table. The problem is resolved in PostgreSQL Anonymizer 3.3.0 and later versions.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- DALIBO PostgreSQL Anonymizer
From 1 · fixed in 3.3.0