CVSS 3.1
7.5 highCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:HHigh (7.5). EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:HExplain CVE-2026-120058 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-120058?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-120058?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-120058 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13 | psqlodbc | no fix listed | DEBIAN-CVE-2026-120058 |
| Debian | 14 | psqlodbc | 1:18.00.0006-1 | DEBIAN-CVE-2026-120058 |
| Ubuntu | 16.04:LTS, 18.04:LTS, 20.04:LTS and 4 more | psqlodbc | no fix listed | UBUNTU-CVE-2026-120058 |
| SUSE | Linux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 5 more | psqlODBC | 18.00.0006-150000.3.14.1 | SUSE-SU-2026:5253-1 |
| SUSE | Linux Enterprise Module for Basesystem 15 SP7, Linux Enterprise Server 15 SP6-LTSS, Linux Enterprise Server for SAP Applications 15 SP6 | psqlODBC | 18.00.0006-150600.3.5.1 | SUSE-SU-2026:5191-1 |
| SUSE | Linux Enterprise Server 12 SP5-LTSS, Linux Enterprise Server LTSS Extended Security 12 SP5 | psqlODBC | 18.00.0006-1.8.1 | SUSE-SU-2026:5192-1 |
| openSUSE | Leap 16.0 | psqlODBC | 18.00.0006-bp160.1.1 | openSUSE-SU-2026:22261-1 |
| openSUSE | Tumbleweed | psqlODBC | 18.00.0006-1.1 | openSUSE-SU-2026:12472-1 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE.
Red Hat rates this Important.
This vulnerability is rated as Important rather than Critical because successful exploitation requires connecting to an untrusted or compromised database server, or an active network interceptor, alongside a specific cursor fetch configuration. Under default driver deployments, clients typically communicate with trusted backend infrastructure using enforced TLS verification, which impedes unauthorized servers from injecting malformed fetch responses. Furthermore, the issue is only reachable when cursor-based fetching (UseDeclareFetch) is explicitly enabled in the ODBC connection profile or data source configuration.
--- CME Mitigation Guidance (2026-11-04) ---
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.
The highest-value action is to validate that subsequent FETCH reply column counts match the initial cursor result layout before writing into the row cache in psqlODBC: upgrade to psqlODBC 18.00.0006 (or the fixed Postgresql Odbc builds), which verify that subsequent FETCH replies match the column layout of the initial cursor result before updating the row cache, closing all 2 injection vectors (malformed FETCH reply returning more columns than the initial cursor result, malformed keyset reply returning fewer columns than expected key fields). Until patched, this is a concern on ODBC clients connecting with UseDeclareFetch enabled without strict server verification, so disable UseDeclareFetch in ODBC data source profiles and enforce strict server certificate verification using sslmode=verify-full or GSSAPI authentication. As a compensating measure, enable Address Space Layout Randomization to hinder attackers from reliably targeting executable memory structures following heap overflow, enable full RELRO and PIE to protect the Global Offset Table and impede overwriting function pointers after heap corruption, and enforce forward-edge Control Flow Integrity or Shadow Call Stack to prevent hijacked control flow from overwritten heap pointers. These controls limit blast radius and contain exploitation, but they do not fix the underlying heap buffer overflow and integer underflow defect — apply the upstream patch to fully remediate.
Highest-impact CME: CME-1311 Input Size and Quantity Bounds Enforcement (high)
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | postgresql-odbc | Affected | |
| Red Hat Enterprise Linux 6 | postgresql-odbc | Affected | |
| Red Hat Enterprise Linux 7 | postgresql-odbc | Affected | |
| Red Hat Enterprise Linux 8 | postgresql-odbc | Affected | |
| Red Hat Enterprise Linux 9 | postgresql-odbc | Affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-120058.