CVE-2026-105617

{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-105617", "assignerOrgId": "f86ef6dc-4d3a-42ad-8f28-e6d5547a5007", "state": "PUBLISHED", "assignerShortName": "PostgreSQL", "dateReserved": "2026-10-05T16:26:51.873Z", "datePublished": "2026-10-28T17:31:48.320Z", "dateUpdated": "2026-11-05T16:58:16.605Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "f86ef6dc-4d3a-42ad-8f28-e6d5547a5007", "shortName": "PostgreSQL", "dateUpdated": "2026-10-28T17:31:48.320Z"}, "title": "PostgreSQL Anonymizer: Cached plans bypass transparent dynamic masking after a role change or a new masking rule", "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."}], "affected": [{"defaultStatus": "unaffected", "product": "PostgreSQL Anonymizer", "vendor": "DALIBO", "versions": [{"lessThan": "3.3.0", "status": "affected", "version": "1", "versionType": "semver"}]}], "problemTypes": [{"descriptions": [{"lang": "en", "cweId": "CWE-200", "type": "CWE", "description": "Exposure of Sensitive Information to an Unauthorized Actor"}]}], "references": [{"url": "https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/695"}], "metrics": [{"format": "CVSS", "cvssV3_1": {"version": "3.1", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N", "baseScore": 5.7, "baseSeverity": "MEDIUM"}}], "workarounds": [{"lang": "en", "value": "Disconnect active sessions after changing a masking rule."}], "credits": [{"lang": "en", "value": "The PostgreSQL Anonymizer project thanks user Ilya Staroverov for reporting this problem."}]}, "adp": [{"metrics": [{"other": {"type": "ssvc", "content": {"timestamp": "2026-11-05T16:58:05.882714Z", "id": "CVE-2026-105617", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "partial"}], "role": "CISA Coordinator", "version": "2.0.3"}}}], "title": "CISA ADP Vulnrichment", "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-11-05T16:58:16.605Z"}}]}}

{"dataType": "CVE_RECORD", "containers": {"adp": [{"title": "CISA ADP Vulnrichment", "metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2026-105617", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "partial"}], "version": "2.0.3", "timestamp": "2026-11-05T16:58:05.882714Z"}}}], "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-11-05T16:58:11.735Z"}}], "cna": {"title": "PostgreSQL Anonymizer: Cached plans bypass transparent dynamic masking after a role change or a new masking rule", "credits": [{"lang": "en", "value": "The PostgreSQL Anonymizer project thanks user Ilya Staroverov for reporting this problem."}], "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"}], "references": [{"url": "https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/695"}], "workarounds": [{"lang": "en", "value": "Disconnect active sessions after changing a masking rule."}], "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."}], "problemTypes": [{"descriptions": [{"lang": "en", "type": "CWE", "cweId": "CWE-200", "description": "Exposure of Sensitive Information to an Unauthorized Actor"}]}], "providerMetadata": {"orgId": "f86ef6dc-4d3a-42ad-8f28-e6d5547a5007", "shortName": "PostgreSQL", "dateUpdated": "2026-10-28T17:31:48.320Z"}}}, "cveMetadata": {"cveId": "CVE-2026-105617", "state": "PUBLISHED", "dateUpdated": "2026-11-05T16:58:16.605Z", "dateReserved": "2026-10-05T16:26:51.873Z", "assignerOrgId": "f86ef6dc-4d3a-42ad-8f28-e6d5547a5007", "datePublished": "2026-10-28T17:31:48.320Z", "assignerShortName": "PostgreSQL"}, "dataVersion": "5.2"}

{"affected": [{"affectedData": [{"defaultStatus": "unaffected", "product": "PostgreSQL Anonymizer", "vendor": "DALIBO", "versions": [{"lessThan": "3.3.0", "status": "affected", "version": "1", "versionType": "semver"}]}], "source": "f86ef6dc-4d3a-42ad-8f28-e6d5547a5007"}], "configurations": [{"nodes": [{"cpeMatch": [{"criteria": "cpe:2.3:a:dalibo:postgresql_anonymizer:*:*:*:*:*:postgresql:*:*", "matchCriteriaId": "06A375DD-F0FB-49E3-82DB-135793DCA922", "versionEndExcluding": "3.3.0", "vulnerable": true}], "negate": false, "operator": "OR"}]}], "cveTags": [], "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."}], "id": "CVE-2026-105617", "lastModified": "2026-11-12T13:37:28.470", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 6.5, "baseSeverity": "MEDIUM", "confidentialityImpact": "HIGH", "integrityImpact": "NONE", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "REQUIRED", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N", "version": "3.1"}, "exploitabilityScore": 2.8, "impactScore": 3.6, "source": "f86ef6dc-4d3a-42ad-8f28-e6d5547a5007", "type": "Secondary"}], "ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-105617", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "role": "CISA Coordinator", "timestamp": "2026-11-05T16:58:05.882714Z", "version": "2.0.3"}}]}, "published": "2026-10-28T18:17:03.510", "references": [{"source": "f86ef6dc-4d3a-42ad-8f28-e6d5547a5007", "tags": ["Broken Link"], "url": "https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/695"}], "sourceIdentifier": "f86ef6dc-4d3a-42ad-8f28-e6d5547a5007", "vulnStatus": "Analyzed", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-200"}], "source": "f86ef6dc-4d3a-42ad-8f28-e6d5547a5007", "type": "Secondary"}]}

{}

{"affected": [{"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "generic", "value": "[1,3.3.0)"}}], "enrichment": {"confidence": 100.0, "confidence_source": "matching", "scores": [{"score": 100.0, "source": "matching"}]}, "original": {"product": "PostgreSQL Anonymizer", "source": "cna", "vendor": "DALIBO"}, "product": "postgresql_anonymizer", "vendor": "dalibo"}], "created": "2026-10-28T18:30:15.305824+00:00", "updated": "2026-10-28T18:45:06.877304+00:00", "vendors": ["dalibo", "dalibo$PRODUCT$postgresql_anonymizer"]}