Is CVE-2026-120059 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-120059 being exploited in the wild.

How severe is CVE-2026-120059?

Medium severity, with a CVSS score of 6.8, published 2 November 2026.

Which products and versions are affected?

PostgreSQL psqlODBC before 18.00.0006.

Is there a fix for CVE-2026-120059?

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-120059 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-120059?

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.

CVE-2026-120059: psqlODBC format string in auto-increment column name

CVE-2026-120059 · Severity: medium · CVSS 6.8 · Published 2026-11-02

psqlODBC is a database driver that connects applications to PostgreSQL. When reading a table with an auto-incrementing column, the driver unsafely uses the column's name as part of a format string, allowing an attacker to read arbitrary application memory or inject malicious content into database queries. An attacker with database access or control over a PostgreSQL server can exploit this to crash applications or expose sensitive data.

Technologies: PostgreSQL psqlODBC. Vendors: PostgreSQL.

Quick answers

Is CVE-2026-120059 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-120059 being exploited in the wild.
How severe is CVE-2026-120059?: Medium severity, with a CVSS score of 6.8, published 2 November 2026.
Which products and versions are affected?: PostgreSQL psqlODBC before 18.00.0006.
Is there a fix for CVE-2026-120059?: 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-120059 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-120059?: 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

The vulnerability is a format string flaw in psqlODBC's handling of updatable cursors over tables without OIDs that contain auto-increment int4 columns. The column name from the server is directly inserted into a printf-style format string without sanitization, then expanded with a single argument when building positioned SELECT, UPDATE, or DELETE statements. An attacker can craft a column name containing format directives (e.g., %x, %s) to read unrelated memory or write data into query text sent to the server.

Affected products

PostgreSQL psqlODBC before 18.00.0006

Timeline

2026-11-02: disclosed

References

https://github.com/postgresql-interfaces/psqlodbc/security/advisories/GHSA-44rq-72jh-x2h8

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.