Live › vulnerability › CVE-2026-120066
When logging is enabled on Unix-like systems, psqlODBC writes logs to a predictable file in /tmp with default, often world-readable permissions, and follows symbolic links. A local user can read another user's query text and data, or redirect log writes to a file of their choice with the victim's privileges.
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 on Unix-like OSes that use psqlODBC with logging enabled, where multiple local users share the machine. Hosts with logging disabled or single-user machines are less exposed. The sources do not describe a remote path.
No product ranges from the sources yet.
18.00.0006 or later is not affected per the description./tmp owned by other users.18.00.0006 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-120066")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.