{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-105617 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-105617 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-105617 is a medium-severity vulnerability in DALIBO PostgreSQL Anonymizer, published on 28 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-105617 and fix it if it is affected.\n\nWhat it is: CVE-2026-105617 is a medium-severity vulnerability in DALIBO PostgreSQL Anonymizer, published on 28 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-105617 in the wild and no public exploit code.\n\nAffected product: DALIBO PostgreSQL Anonymizer. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-105617/ (Markdown: https://insights.sbomify.com/CVE-2026-105617/index.md)","id":"CVE-2026-105617","markdown":"https://insights.sbomify.com/CVE-2026-105617/index.md","name":"CVE-2026-105617","record":{"aliases":["GHSA-pmmg-m528-xf29"],"analysis":null,"analysis_generated_by":null,"assigner":"PostgreSQL","cpe":[],"cvss":{"score":5.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"PostgreSQL Anonymizer: Cached plans bypass transparent dynamic masking after a role change or a new masking rule","id":"CVE-2026-105617","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"PostgreSQL Anonymizer: Masked partitions and child tables are not masked when they are queried through their parent","id":"CVE-2026-105618"},"packages":[],"prev":{"headline":"PostgreSQL Anonymizer: The secret salt and shift of anon are readable by any role in pg_roles or pg_db_role_setting","id":"CVE-2026-105616"},"products":["PostgreSQL Anonymizer"],"published":"2026-10-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-28","vendors":["DALIBO"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-105617/"}