CVE-2026-120066: psqlODBC log files are created with default permissions at a predictable path and follow symbolic links
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.11% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: psqlodbc (Debian:14) 1:18.00.0006-1; psqlODBC (openSUSE:Leap 16.0) 18.00.0006-bp160.1.1; psqlODBC (openSUSE:Tumbleweed) 18.00.0006-1.1.
Low priority for now. Upgrade to psqlodbc (Debian:14) 1:18.00.0006-1; psqlODBC (openSUSE:Leap 16.0) 18.00.0006-bp160.1.1; psqlODBC (openSUSE:Tumbleweed) 18.00.0006-1.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Nov 2, 2026
- Updated
- Nov 2, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- CWE-59
Report tools
Action score
21
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · PostgreSQL
- 5.3
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (PostgreSQL). Independent of NVD's CPE analysis and usually ahead of it.
PostgreSQL psqlODBC
- before 18.00.0006affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | psqlodbc | from 0 | — |
| Debian:14 | psqlodbc | before 1:18.00.0006-1 | 1:18.00.0006-1 |
| openSUSE:Leap 16.0 | psqlODBC | before 18.00.0006-bp160.1.1 | 18.00.0006-bp160.1.1 |
| openSUSE:Tumbleweed | psqlODBC | before 18.00.0006-1.1 | 18.00.0006-1.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | psqlODBC | before 18.00.0006-150600.3.5.1 | 18.00.0006-150600.3.5.1 |
| SUSE:Linux Enterprise Server 12 SP5-LTSS | psqlODBC | before 18.00.0006-1.8.1 | 18.00.0006-1.8.1 |
Same product
postgresql: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-120064psqlODBC does not validate column numbers and row indexes in binding and descriptor functions30Monitor
- CVE-2026-120062psqlODBC SQL injection through SQLSpecialColumns table and schema names30Monitor
- CVE-2026-120061psqlODBC ODBC escape parser stack buffer overflow30Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-120063Nov 2, 2026 · psqlODBC stack buffer overflow when quoting long schema and table names23Monitor
- ← EarlierCVE-2026-120065Nov 2, 2026 · psqlODBC does not escape a server-supplied column name in its updatable-cursor queries28Monitor
- Later →CVE-2026-120067Nov 2, 2026 · psqlODBC stack buffer overflow copying ctid and oid values for updatable cursors23Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:psqlodbc | 1:18.00.0006-1 · Debian:14 | Package registry (OSV) |
| opensuse:psqlODBC | 18.00.0006-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:psqlODBC | 18.00.0006-150600.3.5.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recorded+3 d
- TodayNov 13, 2026+11 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-59 · Improper Link Resolution Before File Access ('Link Following')CVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
- Obfuscated Files or Information: HTML SmugglingT1027.006
- Obfuscated Files or Information: Embedded PayloadsT1027.009
- Boot or Logon Autostart Execution:Shortcut ModificationT1547.009
- Hide Artifacts: Resource ForkingT1564.009
- Hijack Execution Flow: Executable Installer File Permissions WeaknessT1574.005
- Hijack Execution Flow: Services File Permissions WeaknessT1574.010
Change log
- Fix✗ → ✓
- SSVC exploitation— → none
- Exploit maturity— → none
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.