For updatable cursors, which are enabled by default, psqlODBC adds hidden ctid and, for tables with OIDs, oid columns to the query. It copies each value into a 32-byte stack buffer using the length the server sent, without checking it against the buffer size, so a value of 32 bytes or more writes past the buffer. A server not trusted under current SSL settings can send such a value. So can any database user who can create a view with its own column named ctid that the application reads with an updatable cursor. Builds with _FORTIFY_SOURCE abort; other builds overwrite adjacent stack memory. Versions before psqlODBC 18.00.0006 are affected.
CVE-2026-120067
MEDIUMPre-NVD 5.95.9
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 5.9 from GitHub Security Advisory (severity: MODERATE) published 2026-11-02. A secondary CVSS source baseline 5.9; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Also known asEUVD-2026-115380 (ENISA EUVD) · GHSA-pwrw-wjmg-cx9r (GitHub Security Advisories)Source: ENISA EUVD
5.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.9Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
Fixed versions, as the CVE record's CNA (PostgreSQL) states them: "Upgrade to psqlODBC 18.00.0006 or later."
- CVSS v3
- 5.9
- EG Score
- 5.9MEDIUMhigh confidence
- EG Risk
- 27EG Risk 27/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity59% × 45%Impact severity (EG Severity): CVSS 5.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.4% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.3%
- EPSS %ILE
- 28th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (5.9): severity, escalated by confirmed exploitation. This CVE's 5.9 is its impact severity (EG Severity), not escalated.
- EG Severity
- 5.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-03). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 2, 2026
Last Modified
November 2, 2026
References (1)
Vendor Advisories for CVE-2026-120067(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(3 across 3 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| psqlodbc | 1:13.02.0000-2 ... 1:18.00.0006-1 (18 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| psqlodbc | 1:17.00.0004-2 ... 1:18.00.0006-1 (13 versions) |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| psqlodbc | 1:17.00.0004-2 ... 1:18.00.0005-1 (12 versions) |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 14× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.3% · 28th percentile
- 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.3% · 28th percentile
- 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.3% · 28th percentile
- 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.3% · 28th percentile
- 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.3% · 28th percentile
- 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.3% · 28th percentile
- 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.3% · 28th percentile
- 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.3% · 28th percentile
- 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.3% · 28th percentile
- 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.3% · 28th percentile
- 2026-11-04 01:50 UTCEchelonGraph re-scored
- 2026-11-04 01:50 UTCGHSA enrichmentGHSA-pwrw-wjmg-cx9r · GitHub severity MODERATE · GitHub CVSS 5.9
- 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.3% · 28th percentile
- 2026-11-02 20:03 UTCENISA EUVD ID recordedEUVD-2026-115380 · Source: ENISA EUVD
- 2026-11-02 19:28 UTCEchelonGraph re-scored
- 2026-11-02 19:14 UTCEchelonGraph re-scoredFirst assessed: 5.9 MEDIUM
- 2026-11-02 19:12 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
10 shownDebian:12:psqlodbc
Frequently asked(5)
What is CVE-2026-120067?
CVE-2026-120067 is a medium-severity vulnerability; its CVE record was published on November 2, 2026. For updatable cursors, which are enabled by default, psqlODBC adds hidden ctid and, for tables with OIDs, oid columns to the query. It copies each value into a 32-byte stack buffer using the length the server sent, without checking it against the buffer size, so a value of 32 bytes or more writes…
When was CVE-2026-120067 made public?
CVE-2026-120067 was made public on November 2, 2026: that is the date its CVE record's CNA, PostgreSQL, gives for when the vulnerability was made public. The CVE record itself was published on November 2, 2026. EchelonGraph's copy of the record carries a last-modified date of November 2, 2026; the record at its source may have been updated since.
Is CVE-2026-120067 actively exploited?
CVE-2026-120067 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-120067?
CVE-2026-120067 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-120067?
A fix for CVE-2026-120067 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (PostgreSQL) states them: "Upgrade to psqlODBC 18.00.0006 or later." The vendor advisories EchelonGraph has for CVE-2026-120067 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-120067
Is Your Infrastructure Affected by CVE-2026-120067?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.