cve.bz

CVE-2026-120057 Classic Buffer Overflow

7.5 highEPSS 0.2%

High (7.5). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-120 Buffer Copy without Checking Size of Input (Classic Buffer Overflow)
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-120057 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-120057?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-120057?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-120057 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.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13psqlodbcno fix listedDEBIAN-CVE-2026-120057
Debian14psqlodbc1:18.00.0006-1DEBIAN-CVE-2026-120057
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 morepsqlodbcno fix listedUBUNTU-CVE-2026-120057
SUSELinux 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 morepsqlODBC18.00.0006-150000.3.14.1SUSE-SU-2026:5253-1
SUSELinux Enterprise Module for Basesystem 15 SP7, Linux Enterprise Server 15 SP6-LTSS, Linux Enterprise Server for SAP Applications 15 SP6psqlODBC18.00.0006-150600.3.5.1SUSE-SU-2026:5191-1
SUSELinux Enterprise Server 12 SP5-LTSS, Linux Enterprise Server LTSS Extended Security 12 SP5psqlODBC18.00.0006-1.8.1SUSE-SU-2026:5192-1
openSUSELeap 16.0psqlODBC18.00.0006-bp160.1.1openSUSE-SU-2026:22261-1
openSUSETumbleweedpsqlODBC18.00.0006-1.1openSUSE-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

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important severity because memory corruption leading to potential client-side code execution or denial of service can be triggered remotely by an adversarial server or an unauthenticated network adversary. In Red Hat Enterprise Linux, the issue specifically affects client applications that utilize the postgresql-odbc driver to fetch large-object database fields. Systems remain unaffected if applications do not read large-object data or if connections are strictly restricted to trusted database hosts over verified TLS sessions.

Red Hat's mitigation

--- 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 clamp copy lengths against destination buffer sizes when processing large-object read responses in psqlODBC: upgrade to psqlODBC 18.00.0006 (or the fixed Postgresql Odbc builds), which pass the destination buffer size to CC_send_function to clamp copy lengths and reject short fixed-size replies, closing all 2 injection vectors (malicious database server response, man-in-the-middle network response manipulation). Until patched, this is a concern on client applications using psqlODBC to fetch large-object database fields, so avoid fetching large-object columns unless connections enforce sslmode=verify-full or required GSSAPI encryption to trusted database servers. As a compensating measure, enable ASLR to randomize memory layouts and impede reliable arbitrary code execution, compile with stack canaries to detect stack buffer overflows and abort the client process, enable full RELRO and PIE to enforce read-only relocations and hinder memory pointer exploitation, enable Control Flow Integrity or Shadow Call Stack to block control-flow hijacking, and enable FORTIFY_SOURCE to detect buffer overflows into fixed-size buffers and terminate execution. These controls limit blast radius and contain exploitation, but they do not fix the underlying buffer overflow defect — apply the upstream patch to fully remediate.

Highest-impact CME: CME-101 ASLR (Address Space Layout Randomization) (medium)

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10postgresql-odbcAffected
Red Hat Enterprise Linux 6postgresql-odbcAffected
Red Hat Enterprise Linux 7postgresql-odbcAffected
Red Hat Enterprise Linux 8postgresql-odbcAffected
Red Hat Enterprise Linux 9postgresql-odbcAffected

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

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-120 (13).

References

Check your stackJSON