Live › vulnerability › CVE-2026-120063
psqlODBC, the PostgreSQL ODBC driver, copies a schema or table name into a 128-byte stack buffer without a correct length check, so a long name writes up to two bytes past the end. An application that forwards untrusted SQL text to the driver can have its process stack corrupted.
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.
Applications that connect to PostgreSQL through psqlODBC versions before 18.00.0006 and forward untrusted SQL text to the driver are exposed. Applications that only run fixed SQL written by the team, or that do not use this driver, can skip it.
No product ranges from the sources yet.
odbcinst -q -d or the driver's package manager entry) and see whether it is below 18.00.0006.18.00.0006 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
When psqlODBC quotes a schema or table name into a 128-byte stack buffer, its length check lets it write up to two bytes past the end of the buffer for a long name. The names come from the application's SQL text: the table of a statement the driver parses to describe its columns, and the target of the last INSERT when the driver rewrites SELECT @@IDENTITY. In the @@IDENTITY rewrite, a column name sent by the server can also write one byte past the buffer. The bytes written past the buffer are a double quote and a NUL. An application that forwards untrusted SQL text to the driver exposes its process to stack corruption. Versions before psqlODBC 18.00.0006 are affected.
This page as .md · .json · in your agent: get_signal("CVE-2026-120063")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.