{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-120059 in the wild and no public exploit code.","exposure":"","fix":"Upgrade to a fixed version.","what":"CVE-2026-120059 is a medium-severity vulnerability in PostgreSQL psqlODBC, published on 2 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-120059 and fix it if it is affected.\n\nWhat it is: CVE-2026-120059 is a medium-severity vulnerability in PostgreSQL psqlODBC, published on 2 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-120059 in the wild and no public exploit code.\n\nAffected product: PostgreSQL psqlODBC. 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-120059/ (Markdown: https://insights.sbomify.com/CVE-2026-120059/index.md)","id":"CVE-2026-120059","markdown":"https://insights.sbomify.com/CVE-2026-120059/index.md","name":"CVE-2026-120059","record":{"aliases":["DEBIAN-CVE-2026-120059","GHSA-44rq-72jh-x2h8","GHSA-p6rq-g598-qx9f","UBUNTU-CVE-2026-120059"],"analysis":null,"analysis_generated_by":null,"assigner":"PostgreSQL","cpe":[],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-134","name":"Use of Externally-Controlled Format String"}],"description":"For an updatable cursor over a table without OIDs that has an auto-increment int4 column, psqlODBC places that column's name, as reported by the server, into a printf-style format string. It later expands that string with one argument while it builds the WHERE clause of its positioned SELECT, UPDATE, and DELETE statements. A column name that contains format directives makes the driver read unrelated memory, which can crash the application or copy client memory into query text sent to the server. The name can come from a server not trusted under current SSL settings, or from any database user who can create a table that the application reads with an updatable cursor. Versions before psqlODBC 18.00.0006 are affected.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"psqlODBC uses a server-supplied column name as a format string","id":"CVE-2026-120059","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"psqlODBC does not validate server-supplied counts and lengths","id":"CVE-2026-120060"},"nickname":null,"packages":[],"prev":{"headline":"psqlODBC row cache overflow when a later FETCH changes the column count","id":"CVE-2026-120058"},"products":["psqlODBC"],"published":"2026-11-02","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-11-02","vendors":["PostgreSQL"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-120059/"}