Skip to content
Noroxi
NVD / CVE Program· CNA PostgreSQL

CVE-2026-120060: psqlODBC does not validate server-supplied counts and lengths

MediumCVSS 5.9 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 23/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.21% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. 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

psqlODBC trusts counts and lengths in server data in three places. SQLBulkOperations uses a server-supplied row count in a size subtraction that can underflow. SQLStatistics iterates index keys using a server-supplied key count without bounding it to the fixed storage. Bytea octal decoding reads up to two bytes past the end of a truncated escape sequence. A server not trusted under current SSL settings can crash the client or make it read out of bounds. Versions before psqlODBC 18.00.0006 are affected.

Published
Nov 2, 2026
Updated
Nov 2, 2026
EPSS
0.2% · 12th percentile

Report tools

JSON

Action score

23

Monitor

Low priority for now.

CVSS
23 / 40 · 5.9 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · PostgreSQL
5.9
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-120060

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for postgresql records
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

Same product

postgresql: all records

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-120058Nov 2, 2026 · psqlODBC row cache overflow when a later FETCH changes the column count
    30Monitor
  • ← EarlierCVE-2026-120059Nov 2, 2026 · psqlODBC uses a server-supplied column name as a format string
    27Monitor
  • Later →CVE-2026-120063Nov 2, 2026 · psqlODBC stack buffer overflow when quoting long schema and table names
    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

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
low · data can be read
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

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

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.

ATT&CK techniques

—

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