# CVE-2026-120058: psqlODBC row cache overflow when a later FETCH changes the column count


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 2 Nov 2026
- **Updated:** 2 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-120058, GHSA-239q-q7g3-5876, GHSA-6rmx-9q62-4w6m, UBUNTU-CVE-2026-120058

## What is CVE-2026-120058?

CVE-2026-120058 is a high-severity vulnerability in PostgreSQL psqlODBC, published on 2 Nov 2026. 

### Official 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.

Weakness: CWE-787 (Out-of-bounds Write), CWE-191 (Integer Underflow (Wrap or Wraparound))

## Which versions are affected by CVE-2026-120058?


## How do I fix CVE-2026-120058?

Upgrade to a fixed version.

## Is CVE-2026-120058 being exploited?

There is no known exploitation of CVE-2026-120058 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120058 and fix it if it is affected.

What it is: CVE-2026-120058 is a high-severity vulnerability in PostgreSQL psqlODBC, published on 2 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120058 in the wild and no public exploit code.

Affected product: PostgreSQL psqlODBC. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120058/ (Markdown: https://insights.sbomify.com/CVE-2026-120058/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120058
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120058
- OSV: https://osv.dev/vulnerability/CVE-2026-120058

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120058/
Summaries are generated and may contain mistakes; the official description above is the record.