{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-120058 in the wild and no public exploit code.","exposure":"","fix":"Upgrade to a fixed version.","what":"CVE-2026-120058 is a high-severity vulnerability in PostgreSQL psqlODBC, published on 2 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-120058 and fix it if it is affected.\n\nWhat it is: CVE-2026-120058 is a high-severity vulnerability in PostgreSQL psqlODBC, published on 2 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-120058 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-120058/ (Markdown: https://insights.sbomify.com/CVE-2026-120058/index.md)","id":"CVE-2026-120058","markdown":"https://insights.sbomify.com/CVE-2026-120058/index.md","name":"CVE-2026-120058","record":{"aliases":["DEBIAN-CVE-2026-120058","GHSA-239q-q7g3-5876","GHSA-6rmx-9q62-4w6m","UBUNTU-CVE-2026-120058"],"analysis":null,"analysis_generated_by":null,"assigner":"PostgreSQL","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-191","name":"Integer Underflow (Wrap or Wraparound)"}],"description":"psqlODBC sizes its row cache from the column count of a cursor's first result, but recomputes the column count from each later FETCH reply without checking that it matches. A server not trusted under current SSL settings can answer a later FETCH with more columns and make the driver write tuple records past the end of the heap allocation. A keyset reply with fewer columns than the key fields also underflows the unsigned field count. This is reachable with UseDeclareFetch enabled. 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 row cache overflow when a later FETCH changes the column count","id":"CVE-2026-120058","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 uses a server-supplied column name as a format string","id":"CVE-2026-120059"},"nickname":null,"packages":[],"prev":{"headline":"psqlODBC large-object read overflows the application buffer","id":"CVE-2026-120057"},"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":"total"},"state":"PUBLISHED","updated":"2026-11-02","vendors":["PostgreSQL"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-120058/"}