{"api_version":"1","generated_at":"2026-11-12T14:03:31+00:00","cve":"CVE-2026-105617","urls":{"html":"https://cve.report/CVE-2026-105617","api":"https://cve.report/api/cve/CVE-2026-105617.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-105617","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-105617"},"summary":{"title":"PostgreSQL Anonymizer: Cached plans bypass transparent dynamic masking after a role change or a new masking rule","description":"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.","state":"PUBLISHED","assigner":"PostgreSQL","published_at":"2026-10-28 18:17:03","updated_at":"2026-11-12 13:37:28"},"problem_types":["CWE-200","CWE-200 Exposure of Sensitive Information to an Unauthorized Actor"],"metrics":[{"version":"3.1","source":"f86ef6dc-4d3a-42ad-8f28-e6d5547a5007","type":"Secondary","score":"6.5","severity":"MEDIUM","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","baseScore":6.5,"baseSeverity":"MEDIUM","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"REQUIRED","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"NONE","availabilityImpact":"NONE"}},{"version":"3.1","source":"CNA","type":"CVSS","score":"5.7","severity":"MEDIUM","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","data":{"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","version":"3.1"}}],"references":[{"url":"https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/695","name":"https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/695","refsource":"f86ef6dc-4d3a-42ad-8f28-e6d5547a5007","tags":["Broken Link"],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-105617","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-105617","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"DALIBO","product":"PostgreSQL Anonymizer","version":"affected 1 3.3.0 semver","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[{"source":"CNA","title":"","value":"Disconnect active sessions after changing a masking rule.","time":"","lang":"en"}],"exploits":[],"credits":[{"source":"CNA","value":"The PostgreSQL Anonymizer project thanks user Ilya Staroverov for reporting this problem.","lang":"en"}],"nvd_cpes":[{"cve_year":"2026","cve_id":"105617","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"dalibo","cpe5":"postgresql_anonymizer","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"postgresql","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"105617","cve":"CVE-2026-105617","epss":"0.002170000","percentile":"0.122290000","score_date":"2026-11-10","updated_at":"2026-11-11 00:08:18"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"adp":[{"metrics":[{"other":{"content":{"id":"CVE-2026-105617","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"partial"}],"role":"CISA Coordinator","timestamp":"2026-11-05T16:58:05.882714Z","version":"2.0.3"},"type":"ssvc"}}],"providerMetadata":{"dateUpdated":"2026-11-05T16:58:16.605Z","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","shortName":"CISA-ADP"},"title":"CISA ADP Vulnrichment"}],"cna":{"affected":[{"defaultStatus":"unaffected","product":"PostgreSQL Anonymizer","vendor":"DALIBO","versions":[{"lessThan":"3.3.0","status":"affected","version":"1","versionType":"semver"}]}],"credits":[{"lang":"en","value":"The PostgreSQL Anonymizer project thanks user Ilya Staroverov for reporting this problem."}],"descriptions":[{"lang":"en","value":"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."}],"metrics":[{"cvssV3_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","version":"3.1"},"format":"CVSS"}],"problemTypes":[{"descriptions":[{"cweId":"CWE-200","description":"Exposure of Sensitive Information to an Unauthorized Actor","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-10-28T17:31:48.320Z","orgId":"f86ef6dc-4d3a-42ad-8f28-e6d5547a5007","shortName":"PostgreSQL"},"references":[{"url":"https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/695"}],"title":"PostgreSQL Anonymizer: Cached plans bypass transparent dynamic masking after a role change or a new masking rule","workarounds":[{"lang":"en","value":"Disconnect active sessions after changing a masking rule."}]}},"cveMetadata":{"assignerOrgId":"f86ef6dc-4d3a-42ad-8f28-e6d5547a5007","assignerShortName":"PostgreSQL","cveId":"CVE-2026-105617","datePublished":"2026-10-28T17:31:48.320Z","dateReserved":"2026-10-05T16:26:51.873Z","dateUpdated":"2026-11-05T16:58:16.605Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-10-28 18:17:03","lastModifiedDate":"2026-11-12 13:37:28","problem_types":["CWE-200","CWE-200 Exposure of Sensitive Information to an Unauthorized Actor"],"metrics":{"cvssMetricV31":[{"source":"f86ef6dc-4d3a-42ad-8f28-e6d5547a5007","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","baseScore":6.5,"baseSeverity":"MEDIUM","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"REQUIRED","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"NONE","availabilityImpact":"NONE"},"exploitabilityScore":2.8,"impactScore":3.6}],"ssvcV203":[{"source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","ssvcData":{"timestamp":"2026-11-05T16:58:05.882714Z","id":"CVE-2026-105617","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}}]},"configurations":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:a:dalibo:postgresql_anonymizer:*:*:*:*:*:postgresql:*:*","versionEndExcluding":"3.3.0","matchCriteriaId":"06A375DD-F0FB-49E3-82DB-135793DCA922"}]}]}]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"105617","Ordinal":"1","Title":"PostgreSQL Anonymizer: Cached plans bypass transparent dynamic m","CVE":"CVE-2026-105617","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"105617","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"PostgreSQL Anonymizer: Cached plans bypass transparent dynamic m"}]}}}