Skip to content
Noroxi
NVD / CVE Program· CNA PostgreSQL

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

MediumCVSS 5.3 · v3.1—No exploit Fix available

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

Report tools

JSON

Action score

21

Monitor

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.

Follow CVE-2026-120066

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is your version affected? Check it

Noroxi 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 help

Affected 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.

EcosystemPackageAffected rangeFix
Debian:12psqlodbcfrom 0—
Debian:14psqlodbcbefore 1:18.00.0006-11:18.00.0006-1
openSUSE:Leap 16.0psqlODBCbefore 18.00.0006-bp160.1.118.00.0006-bp160.1.1
openSUSE:TumbleweedpsqlODBCbefore 18.00.0006-1.118.00.0006-1.1
SUSE:Linux Enterprise Module for Basesystem 15 SP7psqlODBCbefore 18.00.0006-150600.3.5.118.00.0006-150600.3.5.1
SUSE:Linux Enterprise Server 12 SP5-LTSSpsqlODBCbefore 18.00.0006-1.8.118.00.0006-1.8.1

Other highest-scoring records for the same primary product.

  • CVE-2026-120064psqlODBC does not validate column numbers and row indexes in binding and descriptor functions
    30Monitor
  • CVE-2026-120062psqlODBC SQL injection through SQLSpecialColumns table and schema names
    30Monitor
  • CVE-2026-120061psqlODBC ODBC escape parser stack buffer overflow
    30Monitor

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 names
    23Monitor
  • ← EarlierCVE-2026-120065Nov 2, 2026 · psqlODBC does not escape a server-supplied column name in its updatable-cursor queries
    28Monitor
  • Later →CVE-2026-120067Nov 2, 2026 · psqlODBC stack buffer overflow copying ctid and oid values for updatable cursors
    23Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:psqlodbc1:18.00.0006-1 · Debian:14Package registry (OSV)
opensuse:psqlODBC18.00.0006-1.1 · openSUSE:TumbleweedPackage registry (OSV)
suse:psqlODBC18.00.0006-150600.3.5.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package 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.

  1. Published
  2. Fix recorded+3 d
  3. TodayNov 13, 2026+11 d
EPSS, last 120 days

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

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N

nvd-secondary

Change log

  1. Fix✗ → ✓
  2. SSVC exploitation— → none
  3. 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.

All records