---
id: CVE-2026-105616
title: >-
  PostgreSQL Anonymizer: The secret salt and shift of anon are readable by any
  role in pg_roles or pg_db_role_setting
summary: >-
  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…
severity: medium
cvss: 5.7
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N'
cvssSource: cna
cwe:
  - CWE-200
vendor: DALIBO
product: PostgreSQL Anonymizer
affected:
  - postgresql_anonymizer >= 1 < 3.3.0
published: '2026-10-28'
updated: '2026-10-28'
sourceUpdated: '2026-10-28T17:31:47.686Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-105616'
references:
  - url: 'https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/694'
tags:
  - cve.org
ingestedAt: '2026-10-28T18:15:46.392Z'
epss: 0.00194
epssPercentile: 0.09166
---

## Overview

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.

## Affected

- `postgresql_anonymizer >= 1 < 3.3.0`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.

### Workarounds

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