CVE-2026-105618: PostgreSQL Anonymizer's documentation recommends applying rules on partitions and inheritance tables
Affects postgresql_anonymizerSource GCVE Database
Not known to be exploited · CVSS 5.7 Medium : upgrade to 3.3.0 when convenient.
Data as of 28 Oct 2026, 19:42 UTC
- Patch
- Available – fixed in 3.3.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade dalibo/postgresql_anonymizer to 3.3.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubdalibo/postgresql_anonymizerpkg:github/dalibo/postgresql_anonymizerOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to PostgreSQL Anonymizer version 3.3.0 or later, where this issue is resolved. Applying anonymization rules explicitly on partitions and inheritance tables as recommended by the documentation is necessary to ensure proper data masking.
Description
The PostgreSQL Anonymizer documentation advises applying anonymization rules on partitions and inheritance tables because direct access to these tables is masked, but not when accessed through the parent table. This behavior could lead to unintended data exposure. The issue is addressed in PostgreSQL Anonymizer version 3.3.0 and later.