CVE-2026-105617
mediumPostgreSQL Anonymizer doesn't invalidate plans prepared after a rule was added or a role changed.
PostgreSQL Anonymizer doesn't invalidate plans prepared after a rule was added or a role changed. Users using such plans can still see the unmasked data until the end of the session. The problem is resolved in PostgreSQL Anonymizer 3.3.0 and later versions.
CVSS
6.5
6.5 (CVSS v3.1)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N Severity source: NVD CVSS v3.1 (f86ef6dc-4d3a-42ad-8f28-e6d5547a5007)
Timeline (UTC)
Published: 2026-10-28 18:17
Modified: 2026-10-29 15:29
NVD status: Awaiting Analysis
Last synced 14 hours ago
Verified against the source API 2026-10-29 15:41 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).
Affected products
Not reported by the source (unknown — not "none").
Weakness classification (CWE)
Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.
Mitigation & advisories
No vendor advisory or patch reference tagged by NVD. Check the references below.
References
- https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/695 f86ef6dc-4d3a-42ad-8f28-e6d5547a5007
Data sources
NVD CVE API 2.0 — fetched 2026-10-29 15:41 UTC · record ↗