Live › vulnerability › CVE-2026-120060
psqlODBC is the PostgreSQL ODBC driver. Three code paths trust row counts, key counts and escape lengths sent by the server, so a malicious or untrusted server can crash the client or cause out-of-bounds reads.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-02 19:24 UTC. All times on this page are UTC.
Systems that use the psqlODBC driver to connect to PostgreSQL servers, especially where the server is not fully trusted under the current SSL settings. A server the team controls and fully trusts is a lower risk. Teams that do not use psqlODBC can skip it.
No product ranges from the sources yet.
18.00.0006.18.00.0006 are affected; move to 18.00.0006 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-120060")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.