CVE-2026-105619EUVD-2026-112291GHSA-322M-RVMJ-Q79H
PostgreSQL Anonymizer: Masking rules of the tables are not applied through security_invoker views
- 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 that masks sensitive data in PostgreSQL databases, fails to apply its masking rules to data queried through views created with security_invoker, so users of those views can see unmasked values that should have been hidden.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
PostgreSQL Anonymizer doesn't mask data accessed thru a security_invoker view. 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