# CVE-2026-120066: psqlODBC log files are created with default permissions at a predictable path and follow symbolic links


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 2 Nov 2026
- **Updated:** 2 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-120066, GHSA-rvv3-vcvv-5fqj, GHSA-wj7r-6pj3-62g8, UBUNTU-CVE-2026-120066

## What is CVE-2026-120066?

CVE-2026-120066 is a medium-severity vulnerability in PostgreSQL psqlODBC, published on 2 Nov 2026. 

### Official 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.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2026-120066?


## How do I fix CVE-2026-120066?

Upgrade to a fixed version.

## Is CVE-2026-120066 being exploited?

There is no known exploitation of CVE-2026-120066 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120066 and fix it if it is affected.

What it is: CVE-2026-120066 is a medium-severity vulnerability in PostgreSQL psqlODBC, published on 2 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120066 in the wild and no public exploit code.

Affected product: PostgreSQL psqlODBC. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120066/ (Markdown: https://insights.sbomify.com/CVE-2026-120066/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120066
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120066
- OSV: https://osv.dev/vulnerability/CVE-2026-120066

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120066/
Summaries are generated and may contain mistakes; the official description above is the record.