Quick answers
- Is CVE-2026-120065 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120065 being exploited in the wild.
- How severe is CVE-2026-120065?
- High severity, with a CVSS score of 7.1, published 2 November 2026.
- Which products and versions are affected?
- PostgreSQL psqlODBC before 18.00.0006.
- Is there a fix for CVE-2026-120065?
- Yes: fixed in psqlODBC 18.00.0006. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-120065 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-120065?
- 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
Technical details
psqlODBC uses column names reported by the server in keyset queries and positioned UPDATE/DELETE statements for row identification without properly escaping double quotes within those names. An attacker who can create a table with a column name containing a double quote character can break out of the quoted identifier context and inject arbitrary SQL. This affects updatable cursors over tables without OIDs that have an auto-increment int4 column, requiring either database write access or a compromised/untrusted PostgreSQL server.
Affected products
- PostgreSQL psqlODBC before 18.00.0006
Timeline
- 2026-11-02: disclosed