{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-11945 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-11945 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-11945 is a medium-severity SQL injection vulnerability in DALIBO PostgreSQL Anonymizer, published on 11 Jun 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-11945 and fix it if it is affected.\n\nWhat it is: CVE-2026-11945 is a medium-severity SQL injection vulnerability in DALIBO PostgreSQL Anonymizer, published on 11 Jun 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-11945 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-11945/ (Markdown: https://insights.sbomify.com/CVE-2026-11945/index.md)","id":"CVE-2026-11945","markdown":"https://insights.sbomify.com/CVE-2026-11945/index.md","name":"CVE-2026-11945","record":{"aliases":["GHSA-g5vm-7gwv-45rj"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"PostgreSQL Anonymizer","requires_auth":"high_privilege","summary":"A SQL injection vulnerability in PostgreSQL Anonymizer allows attackers to execute malicious code with superuser privileges via crafted JSON imports.","user_interaction":"required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"PostgreSQL","cpe":[{"product":"postgresql_anonymizer","vendor":"dalibo"}],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/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 JSON document and placing malicious code inside a particular key-value pair. If a superuser calls the import_database_rules() or import_roles_rules() functions, the malicious code is executed with superuser privileges. The problem is resolved in PostgreSQL Anonymizer 3.1.1 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: SQL injection in the rules import functions","id":"CVE-2026-11945","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":"GetEndpoints Memory Exhaustion in open62541","id":"CVE-2026-11946"},"packages":[],"prev":{"headline":"openSIS Classic 9.3 - Authenticated path traversal in SentMail attachment download","id":"CVE-2026-11944"},"products":["PostgreSQL Anonymizer"],"published":"2026-06-11","related":[{"cvss_score":4.3,"headline":"PostgreSQL Anonymizer: Unrestricted function can leak the secret salt","id":"CVE-2026-13455","kev_date_added":null,"published":"2026-06-30"}],"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-06-12","vendors":["DALIBO"]},"summary":"A SQL injection vulnerability in PostgreSQL Anonymizer allows attackers to execute malicious code with superuser privileges via crafted JSON imports.","url":"https://insights.sbomify.com/CVE-2026-11945/"}