{"id":"CVE-2026-105616","state":"PUBLISHED","title":"PostgreSQL Anonymizer: The secret salt and shift of anon are readable by any role in pg_roles or pg_db_role_setting","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.","publishedAt":"2026-10-28T17:31:47.686Z","updatedAt":"2026-10-28T17:31:47.686Z","severity":{"score":5.7,"label":"Medium","version":"3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N","source":"PostgreSQL"},"assigner":"PostgreSQL","products":["DALIBO PostgreSQL Anonymizer"],"affected":[{"vendor":"DALIBO","product":"PostgreSQL Anonymizer","defaultStatus":"unaffected","versions":[{"version":"1","status":"affected","lessThan":"3.3.0","versionType":"semver"}]}],"references":["https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/694"],"weaknesses":["CWE-200"],"ingestedAt":"2026-10-29T20:10:23.711Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2026/105xxx/CVE-2026-105616.json","commit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-105616","state":"PUBLISHED","datePublished":"2026-10-28T17:31:47.686Z","dateUpdated":"2026-10-28T17:31:47.686Z","assignerShortName":"PostgreSQL","assignerOrgId":"f86ef6dc-4d3a-42ad-8f28-e6d5547a5007","dateReserved":"2026-10-05T16:26:51.873Z"},"containers":{"cna":{"title":"PostgreSQL Anonymizer: The secret salt and shift of anon are readable by any role in pg_roles or pg_db_role_setting","descriptions":[{"lang":"en","value":"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":[{"vendor":"DALIBO","product":"PostgreSQL Anonymizer","defaultStatus":"unaffected","versions":[{"version":"1","status":"affected","lessThan":"3.3.0","versionType":"semver"}]}],"references":[{"url":"https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/694"}],"metrics":[{"format":"CVSS","cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N","baseScore":5.7,"baseSeverity":"MEDIUM"}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-200","lang":"en","type":"CWE","description":"Exposure of Sensitive Information to an Unauthorized Actor"}]}],"providerMetadata":{"shortName":"PostgreSQL","orgId":"f86ef6dc-4d3a-42ad-8f28-e6d5547a5007","dateUpdated":"2026-10-28T17:31:47.686Z"},"workarounds":[{"lang":"en","value":"Configure the salt in the postgresql.conf file (or one of it's includes)."}],"credits":[{"lang":"en","value":"The PostgreSQL Anonymizer project thanks user Ilya Staroverov for reporting this problem."}]}}}}