CVE-2026-120063
Awaiting Analysis Awaiting Analysis - Queue

Stack Buffer Overflow in psqlODBC Driver

Publication date: 2026-11-02

Last updated on: 2026-11-02

Assigner: PostgreSQL

Description
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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-02
Last Modified
2026-11-02
Generated
2026-11-02
AI Q&A
2026-11-02
EPSS Evaluated
N/A
NVD
CVE-2026-120063

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
PostgreSQL psqlODBC 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-787 The product writes data past the end, or before the beginning, of the intended buffer.
CWE-121 A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves a stack buffer overflow in psqlODBC when quoting schema or table names. The driver uses a 128-byte stack buffer but allows writing up to two extra bytes past the end for long names. These extra bytes are a double quote and a null terminator. The names come from untrusted SQL text parsed by the driver, such as table names in statements or column names in @@IDENTITY rewrites. This can lead to stack corruption if the application processes untrusted SQL.

Detection Guidance

This vulnerability is specific to psqlODBC versions before 18.00.0006. To detect it, check the installed version of psqlODBC on your system using commands like 'psqlodbc --version' or by inspecting package managers such as 'rpm -qa | grep psqlodbc' or 'dpkg -l | grep psqlodbc'.

Impact Analysis

If you use an affected version of psqlODBC and your application forwards untrusted SQL text to the driver, an attacker could exploit this to corrupt the stack memory of your application process. This may result in crashes, arbitrary code execution, or other unexpected behavior depending on the application's context and security controls.

Compliance Impact

This vulnerability could impact compliance by increasing the risk of data breaches or unauthorized code execution if exploited. For GDPR, it may affect integrity and confidentiality requirements. For HIPAA, it could compromise protected health information integrity. Organizations must assess risk exposure and apply patches to maintain compliance with security controls.

Mitigation Strategies

Upgrade psqlODBC to version 18.00.0006 or later immediately. Avoid forwarding untrusted SQL text to the driver until the upgrade is complete. Monitor for unusual application behavior that may indicate exploitation attempts.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-120063. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...