CVE-2026-105616

PostgreSQL Anonymizer: The secret salt and shift of anon are readable by any role in pg_roles or pg_db_role_setting

Published Oct 28, 2026 CVSS 3.1 · 5.7 Medium EPSS < 1% KEV · Not listed
Description
PostgreSQL restricts acces to the salt and shift via the `SHOW` command for users not member of `pg_read_all_settings`. But they are visible in `pg_db_role_setting` or `pg_roles` if they were set on the database, user or both. PostgreSQL Anonymizer's documentation recommends to use ALTER DATABASE / ALTER ROLE for the salt. The problem is resolved in PostgreSQL Anonymizer 3.3.0 and later versions.

Analysis

AI-generated

Technical impact

PostgreSQL Anonymizer stores a secret salt and shift value that are meant to protect data. The current implementation incorrectly allows any role that can query the system catalogs pg_roles or pg_db_role_setting to view these values, exposing them as a database secret. This vulnerability is a classic information‑disclosure weakness (CWE‑200) that could let an attacker reverse the anonymization process and recover the original data, effectively breaching confidentiality.

Affected Systems

Dalibo’s PostgreSQL Anonymizer extension is affected. All versions before 3.3.0 contain the flaw because the salt and shift are stored in database‑level settings that are readable by any role with access to pg_roles or pg_db_role_setting. The issue is fixed in 3.3.0 and later releases. Organizations using older Anonymizer versions on PostgreSQL databases, particularly those with permissive role configurations, are at risk.

Risk and Exploitability

The CVSS score of 5.7 indicates moderate severity. Exploitation requires an authenticated database user that can read the system catalogs; the most likely scenario is an internal user with broad privileges or a compromised account. Since EPSS is unavailable and the vulnerability is not in the KEV catalog, the current public exploitation probability is unknown. Nevertheless, because the exposed data can reveal sensitive information, a moderate risk assessment is prudent.

Remediation

Vendor Workaround

Configure the salt in the postgresql.conf file (or one of it's includes).


OpenCVE Recommended Actions

  • Upgrade PostgreSQL Anonymizer to version 3.3.0 or newer to remove the secret salt and shift visibility issue.
  • If an upgrade is not immediately possible, configure the salt value in postgresql.conf (or its includes) so that it is not stored in pg_roles or pg_db_role_setting, following the documented workaround.
  • Restrict access to pg_roles and pg_db_role_setting by revoking pg_read_all_settings from untrusted roles, ensuring that only administrative roles retain read privileges to these catalogs.

Generated by OpenCVE AI on October 28, 2026 at 18:53 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:dalibo:postgresql_anonymizer:*:*:*:*:*:postgresql:*:*
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Dalibo
Dalibo postgresql Anonymizer
Vendors & Products Dalibo
Dalibo postgresql Anonymizer
Type Values Removed Values Added
Description PostgreSQL restricts acces to the salt and shift via the `SHOW` command for users not member of `pg_read_all_settings`. But they are visible in `pg_db_role_setting` or `pg_roles` if they were set on the database, user or both. PostgreSQL Anonymizer's documentation recommends to use ALTER DATABASE / ALTER ROLE for the salt. The problem is resolved in PostgreSQL Anonymizer 3.3.0 and later versions.
Title PostgreSQL Anonymizer: The secret salt and shift of anon are readable by any role in pg_roles or pg_db_role_setting
Weaknesses CWE-200
References
Metrics cvssV3_1

{'score': 5.7, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N'}

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

Sources

Status
PUBLISHED
Assigner
PostgreSQL
Published
Updated
Nov 5, 2026, 4:58 PM
Reserved
Oct 5, 2026, 4:26 PM
Status
Analyzed
Published
Oct 28, 2026, 6:17 PM
Modified
Nov 10, 2026, 9:48 PM