CVE-2026-105616: postgresql_anonymizer · PostgreSQL restricts acces to the salt and shift via the SHOW command for users not member of
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. Until then, restrict access to system catalog tables such as pg_db_role_setting and pg_roles to trusted users only. Follow PostgreSQL Anonymizer documentation recommendations to set salts using ALTER DATABASE or ALTER ROLE commands to minimize exposure.
Description
PostgreSQL restricts access to the salt and shift parameters via the SHOW command for users who are not members of the pg_read_all_settings role. However, these sensitive values remain visible in the pg_db_role_setting or pg_roles tables if set at the database or user level. The PostgreSQL Anonymizer documentation recommends setting the salt using ALTER DATABASE or ALTER ROLE commands. This issue is resolved in PostgreSQL Anonymizer version 3.3.0 and later.