# CVE-2026-120061: psqlODBC ODBC escape parser stack buffer overflow


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/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-120061, GHSA-hfm6-qfx8-v4xq, GHSA-rwj3-5rgf-rr95, UBUNTU-CVE-2026-120061

## What is CVE-2026-120061?

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

### Official description

The psqlODBC parser for ODBC escape sequences in application SQL text writes the argument offsets of a {fn} escape into a fixed 16-entry stack array without a bound and does not initialize the array. An escape with too many arguments overflows the stack, and a reference to an unsupplied argument copies arbitrary bytes into the query. The copy of a {d}, {t}, {ts}, or {escape} body also writes one byte past a 128-byte stack buffer. An application that forwards untrusted SQL text to the driver exposes its process to memory corruption. Versions before psqlODBC 18.00.0006 are affected.

Weakness: CWE-457 (Use of Uninitialized Variable), CWE-193 (Off-by-one Error), CWE-121 (Stack-based Buffer Overflow)

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


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

Upgrade to a fixed version.

## Is CVE-2026-120061 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120061 is a high-severity vulnerability in PostgreSQL psqlODBC, published on 2 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120061 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-120061/ (Markdown: https://insights.sbomify.com/CVE-2026-120061/index.md)
```

## Sources

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

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