Live › vulnerability › CVE-2026-105616
Go to dashboardPostgreSQL Anonymizer hides its salt and shift from users who lack pg_read_all_settings when read through SHOW. The same values remain visible in pg_db_role_setting and pg_roles when they were set with ALTER DATABASE or ALTER ROLE, so any role that can read those catalogs can recover them.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 18:34 UTC. All times on this page are UTC.
Teams running PostgreSQL Anonymizer whose anonymization salt or shift was set with ALTER DATABASE or ALTER ROLE, as its documentation recommends. Any database role that can read pg_db_role_setting or pg_roles can see those values, so the exposure extends beyond administrators. Installations that do not use the extension, or that have upgraded to 3.3.0 or later, can skip it.
No product ranges from the sources yet.
SELECT extversion FROM pg_extension WHERE extname = 'anon';); versions before 3.3.0 are affected.pg_db_role_setting and pg_roles.3.3.0 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-105616")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.