Project Subscriptions
No data.
No advisories yet.
Solution
Upgrade to psqlODBC 18.00.0006 or later. On Unix-like systems, log files are opened with mode 0600 and O_NOFOLLOW, and an existing log file is used only if it is a regular file owned by the user running the application.
Workaround
Leave Debug and CommLog disabled in production. If logging is needed, set Logdir in the driver's section of odbcinst.ini (PostgreSQL Unicode or PostgreSQL ANSI) to a directory writable only by the user running the application.
Mon, 02 Nov 2026 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | psqlODBC log files are created with default permissions at a predictable path and follow symbolic links | |
| Weaknesses | CWE-59 CWE-732 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: PostgreSQL
Published:
Updated: 2026-11-02T19:37:32.927Z
Reserved: 2026-10-30T19:25:18.920Z
Link: CVE-2026-120066
No data.
Status : Awaiting Analysis
Published: 2026-11-02T19:18:03.983
Modified: 2026-11-02T19:34:23.993
Link: CVE-2026-120066
No data.
OpenCVE Enrichment
No data.