CVE-2026-120062
Awaiting Analysis Awaiting Analysis - Queue

SQL Injection in psqlODBC via SQLSpecialColumns

Publication date: 2026-11-02

Last updated on: 2026-11-02

Assigner: PostgreSQL

Description
SQLSpecialColumns in psqlODBC splices the table and schema names it receives into its catalog query without escaping them, while the other catalog functions escape them. An application that passes an untrusted table or schema name to SQLSpecialColumns lets the caller execute arbitrary SQL with the privileges of the connection. 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-120062

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-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

SQLSpecialColumns in psqlODBC does not properly escape table and schema names when constructing SQL queries. This allows an attacker to inject arbitrary SQL commands if they can control these names. The vulnerability exists because other catalog functions in psqlODBC do escape these names, but SQLSpecialColumns does not.

Detection Guidance

To detect this vulnerability, check the version of psqlODBC installed on your system. If it is earlier than version 18.00.0006, your system is vulnerable. Use commands like 'psqlodbc --version' or check package managers (e.g., 'dpkg -l | grep psqlodbc' for Debian-based systems).

Review applications using SQLSpecialColumns to ensure they do not pass untrusted table or schema names. Monitor database logs for unusual SQL queries or unauthorized access attempts.

Impact Analysis

If you use an application that passes untrusted table or schema names to SQLSpecialColumns, an attacker could execute arbitrary SQL commands with the privileges of your database connection. This could lead to data theft, data manipulation, or unauthorized access to sensitive information.

Compliance Impact

This vulnerability could lead to unauthorized access or exposure of sensitive data, which may violate GDPR's data protection requirements or HIPAA's security and privacy rules. Organizations using affected versions of psqlODBC may face compliance violations if exploited.

Mitigation Strategies

Upgrade psqlODBC to version 18.00.0006 or later immediately. This version addresses the improper escaping of table and schema names in SQLSpecialColumns.

Audit applications using SQLSpecialColumns to ensure they do not accept untrusted input for table or schema names. Implement input validation and parameterized queries to prevent SQL injection.

Restrict database user privileges to the minimum required for operations. Monitor database activity for suspicious queries or unauthorized access.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-120062. 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...