CVE-2026-120066
Awaiting Analysis Awaiting Analysis - Queue

Information Disclosure in psqlODBC via Log File Permissions

Vulnerability report for CVE-2026-120066, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-02

Last updated on: 2026-11-02

Assigner: PostgreSQL

Description

On Unix-like systems, when logging is enabled, psqlODBC creates its log files in /tmp by default, named from the program name, user name, and process ID, with the default permissions, typically world-readable, and follows symbolic links when opening them. A local user can read query text and data from another user's logs, and can place a symbolic link at the predictable path so that the driver appends log data to a file of the attacker's choosing with the victim's privileges. 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

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-732 The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
CWE-59 The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects psqlODBC on Unix-like systems. When logging is enabled, the driver creates log files in /tmp with predictable names based on the program name, user name, and process ID. These log files are typically world-readable and follow symbolic links. A local attacker can read another user's query text and data from these logs or manipulate them to write log data to a file of their choice using the victim's privileges.

Detection Guidance

Check for suspicious log files in /tmp with names matching psqlODBC log patterns (e.g., psqlODBC_<user>_<pid>.log). Inspect symbolic links pointing to these files. Review file permissions to ensure logs are not world-readable.

Impact Analysis

If you use psqlODBC on a Unix-like system with logging enabled, a local attacker could access sensitive data from your queries or manipulate log files to write data to arbitrary locations. This could lead to information disclosure or unauthorized file modifications.

Compliance Impact

This vulnerability could violate compliance requirements such as GDPR or HIPAA by exposing sensitive data through insecure log handling. Unauthorized access to query data or log manipulation may result in data breaches, leading to potential legal and regulatory penalties.

Mitigation Strategies

Upgrade psqlODBC to version 18.00.0006 or later. Restrict permissions on /tmp to prevent unauthorized access. Disable logging if not required or configure it to use a secure directory with strict permissions.

Chat Assistant

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