Quick answers
- Is CVE-2026-120061 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120061 being exploited in the wild.
- How severe is CVE-2026-120061?
- High severity, with a CVSS score of 7.5, published 2 November 2026.
- Which products and versions are affected?
- PostgreSQL psqlODBC before 18.00.0006.
- Is there a fix for CVE-2026-120061?
- Yes: fixed in psqlODBC 18.00.0006 and later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-120061 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-120061?
- Check whether you run PostgreSQL psqlODBC at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: psqlODBC 18.00.0006 and later
Technical details
The ODBC escape sequence parser writes argument offsets into a fixed 16-entry stack array without bounds checking, and reads from an unsupplied argument position can copy arbitrary memory bytes into the query. Additionally, the parser writes one byte past a 128-byte stack buffer when processing {d}, {t}, {ts}, or {escape} escape bodies. An attacker submitting SQL with excessive escape arguments or specially crafted escape syntax triggers stack buffer overflow and out-of-bounds writes.
Affected products
- PostgreSQL psqlODBC before 18.00.0006
Timeline
- 2026-11-02: disclosed