CVE-2026-120057: psqlODBC large-object read overflows the application buffer
Noroxi assessment
Priority: Monitor (action score 30/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.24% (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 copies the reply to a large-object read (loread) into the application's buffer using the length sent by the server, without comparing it to the buffer size. A server not trusted under current SSL settings, or a man-in-the-middle, can return more bytes than the buffer holds and overwrite adjacent memory in the client process with server-chosen bytes. Fetching any large-object column is sufficient to trigger it. Versions before psqlODBC 18.00.0006 are affected.
- Published
- Nov 2, 2026
- Updated
- Nov 2, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-120
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · PostgreSQL
- 7.5
- 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-109448Oct 12, 2026 · psqlODBC SQLBindParameter heap memory corruption when binding more than 32767 parameters23Monitor
- Later →CVE-2026-120058Nov 2, 2026 · psqlODBC row cache overflow when a later FETCH changes the column count30Monitor
- Later →CVE-2026-120059Nov 2, 2026 · psqlODBC uses a server-supplied column name as a format string27Monitor
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
- 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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.
The bug in code
The whole CWE-120 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
char buf[256];
memcpy(buf, pkt->data, pkt->len);Fixed
char buf[256];
if (pkt->len > sizeof(buf)) {
return -EINVAL;
}
memcpy(buf, pkt->data, pkt->len);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)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
- Overflow Variables and TagsCAPEC-46likelihood: High · High
ATT&CK techniques
—
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.