{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-9617 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-9617 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-9617 is a medium-severity SQL injection vulnerability in DALIBO PostgreSQL Anonymizer, published on 27 May 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-9617 and fix it if it is affected.\n\nWhat it is: CVE-2026-9617 is a medium-severity SQL injection vulnerability in DALIBO PostgreSQL Anonymizer, published on 27 May 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-9617 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-9617/ (Markdown: https://insights.sbomify.com/CVE-2026-9617/index.md)","id":"CVE-2026-9617","markdown":"https://insights.sbomify.com/CVE-2026-9617/index.md","name":"CVE-2026-9617","record":{"aliases":["GHSA-2qfw-46cx-cgv6"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"PostgreSQL Anonymizer extension","requires_auth":"high_privilege","summary":"A malicious column name in PostgreSQL Anonymizer allows SQL injection, enabling privilege escalation to superuser when the k-anonymity function is executed.","user_interaction":"required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"PostgreSQL","cpe":[{"product":"anonymizer","vendor":"dalibo"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"PostgreSQL Anonymizer contains a vulnerability that allows a user to gain superuser privileges by creating a table and placing malicious code inside a column identifier. If a superuser calls the k-anonymity function, the malicious code is executed with superuser privileges. The risk is higher with PostgreSQL 14 or with instances upgraded from PostgreSQL 14 or a prior version. With PostgreSQL 15 and later, the creation permission on the public schema is revoked by default and this exploit can only be achieved by a user who was explicitly granted the CREATE TABLE privilege. The problem is resolved in PostgreSQL Anonymizer 3.1.0 and further 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: malicious column name allows SQL injection via anon.k_anonymity() function","id":"CVE-2026-9617","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"PeachPay \u003c= 1.120.46 - Cross-Site Request Forgery to Stripe Unlink","id":"CVE-2026-9618"},"packages":[],"prev":{"headline":"Missing authorization in Generate Security.txt","id":"CVE-2026-9616"},"products":["PostgreSQL Anonymizer"],"published":"2026-05-27","related":[{"cvss_score":8,"headline":"SQL Injection in PostgreSQL Anonymizer 1.2 allows table owner to gain superuser privileges via masking rule","id":"CVE-2024-2338","kev_date_added":null,"published":"2024-03-08"},{"cvss_score":8,"headline":"Improper Input Validation in PostgreSQL Anonymizer 1.2 allows table owner to gain superuser privileges via masking rule","id":"CVE-2024-2339","kev_date_added":null,"published":"2024-03-08"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-28","vendors":["DALIBO"]},"summary":"A malicious column name in PostgreSQL Anonymizer allows SQL injection, enabling privilege escalation to superuser when the k-anonymity function is executed.","url":"https://insights.sbomify.com/CVE-2026-9617/"}