Skip to content
Heist/ feed
Back to feed
Medium

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

Type: advisorySources: Official CVE List

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.

Products
PostgreSQL Anonymizer
Affected versions
Not specified
Fixed versions
Not specified
CVEs
CVE-2026-105616
Confirmed fixed CVEs
Not specified
Updated in this feed
1 Nov 2026, 20:24 UTC · Revision 1

Source evidence

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

core-cve · Original source

Published 28 Oct 2026, 17:31 UTC

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.

cve:CVE-2026-105616

PostgreSQL Anonymizer

Fixed versions: Not specified

Complete source record
{
  "id": "7bbc83030d7aa845374c9e7be9936a13cb9e3eb460cf81c2deb12de86bb95127",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-105616",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "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 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.",
    "evidence": "cve:CVE-2026-105616",
    "products": [
      {
        "name": {
          "value": "PostgreSQL Anonymizer",
          "evidence": "/containers/cna/affected/0/product"
        },
        "prerequisites": [],
        "fixed_versions": [],
        "affected_versions": []
      }
    ],
    "severity": "medium",
    "structured": {
      "id": "CVE-2026-105616",
      "aliases": [
        "CVE-2026-105616"
      ],
      "metrics": [
        {
          "format": "CVSS",
          "cvssV3_1": {
            "version": "3.1",
            "baseScore": 5.7,
            "baseSeverity": "MEDIUM",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N"
          }
        }
      ],
      "affected": [
        {
          "vendor": "DALIBO",
          "product": "PostgreSQL Anonymizer",
          "versions": [
            {
              "status": "affected",
              "version": "1",
              "lessThan": "3.3.0",
              "versionType": "semver"
            }
          ],
          "defaultStatus": "unaffected"
        }
      ],
      "modified": "2026-10-28T17:31:47.686Z",
      "provider": "cve",
      "references": [
        "https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/694"
      ],
      "provider_metadata": {
        "cna": {
          "orgId": "f86ef6dc-4d3a-42ad-8f28-e6d5547a5007",
          "shortName": "PostgreSQL",
          "dateUpdated": "2026-10-28T17:31:47.686Z"
        }
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-105616",
        "evidence": "/cveMetadata/cveId"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/containers/cna/metrics"
  },
  "source_id": "core-cve",
  "document_id": 466432,
  "published_at": "2026-10-28T17:31:47.686+00:00"
}