Medium
PostgreSQL Anonymizer: Cached plans bypass transparent dynamic masking after a role change or a new masking rule
Type: advisorySources: Official CVE List
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.
- Products
- PostgreSQL Anonymizer
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-105617
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 1 Nov 2026, 20:24 UTC · Revision 1
Source evidence
PostgreSQL Anonymizer: Cached plans bypass transparent dynamic masking after a role change or a new masking rule
core-cve · Original sourcePublished 28 Oct 2026, 17:31 UTC
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.
cve:CVE-2026-105617
PostgreSQL Anonymizer
Fixed versions: Not specified
Complete source record
{
"id": "492c3e58c609d27e4071b8920390455596ac8cf948c2c22fa58099628d2cfd8d",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-105617",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "PostgreSQL Anonymizer: Cached plans bypass transparent dynamic masking after a role change or a new masking rule",
"summary": "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.",
"evidence": "cve:CVE-2026-105617",
"products": [
{
"name": {
"value": "PostgreSQL Anonymizer",
"evidence": "/containers/cna/affected/0/product"
},
"prerequisites": [],
"fixed_versions": [],
"affected_versions": []
}
],
"severity": "medium",
"structured": {
"id": "CVE-2026-105617",
"aliases": [
"CVE-2026-105617"
],
"metrics": [
{
"format": "CVSS",
"cvssV3_1": {
"version": "3.1",
"baseScore": 5.7,
"baseSeverity": "MEDIUM",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/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:48.320Z",
"provider": "cve",
"references": [
"https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/695"
],
"provider_metadata": {
"cna": {
"orgId": "f86ef6dc-4d3a-42ad-8f28-e6d5547a5007",
"shortName": "PostgreSQL",
"dateUpdated": "2026-10-28T17:31:48.320Z"
}
}
},
"related_cves": [
{
"value": "CVE-2026-105617",
"evidence": "/cveMetadata/cveId"
}
],
"security_relevant": true,
"severity_evidence": "/containers/cna/metrics"
},
"source_id": "core-cve",
"document_id": 466433,
"published_at": "2026-10-28T17:31:48.32+00:00"
}