CVE-2026-120060

Description

psqlODBC trusts counts and lengths in server data in three places. SQLBulkOperations uses a server-supplied row count in a size subtraction that can underflow. SQLStatistics iterates index keys using a server-supplied key count without bounding it to the fixed storage. Bytea octal decoding reads up to two bytes past the end of a truncated escape sequence. A server not trusted under current SSL settings can crash the client or make it read out of bounds. Versions before psqlODBC 18.00.0006 are affected.

Severity
MEDIUM
CVSS v3
5.9
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:H · source cna
Exploit chance (EPSS)
0.216%
chance of exploitation in the next 30 days
higher than 12.1% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
None public
Exploit references (NVD and CNA): 0
Metasploit modules: 0
Nuclei templates: 0

Weakness

CISA SSVC decision points

Exploitationnone
Automatableno
Technical impactpartial
Scored2026-11-02

Timeline

  1. 2026-11-02Published by the CNA19:09 UTC
  2. 2026-11-02CISA SSVC decision recordedsame day

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
postgresql psqlodbcfrom 0 before 18.00.0006fixed in 18.00.000618.00.0006

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources