CVE-2026-119924 Out-of-bounds Read

7.2 highEPSS 0.5%

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

On this page

Severity
Ask an AI about this CVE
Affected
Versions
Attack patterns (CAPEC)
References
Your exposure

An out-of-bounds read in the TDS RPC procedure-name parser in the Babelfish for PostgreSQL extension versions 1.0-1.5, 2.1-2.15, 3.1-3.12, 4.0-4.8, 5.1-5.4 and in Amazon Aurora PostgreSQL with Babelfish might allow remote authenticated users to read adjacent process memory or cause a denial of service via a malformed TDS RPC request to the TDS port (default 1433). To remediate this issue, we recommend users upgrade to Babelfish for PostgreSQL extension versions 4.10, 5.6, 6.1 or later. As a workaround, restrict network access to the TDS port (default 1433). Customers using Amazon Aurora PostgreSQL with Babelfish should upgrade their cluster to Aurora PostgreSQL 13.9.16 (1.5.5), 13.23.3 (1.17.2), 14.6.16 (2.3.5), 14.17.8 (2.12.4), 14.18.6 (2.13.3), 14.19.5 (2.14.2), 14.20.5 (2.15.2), 14.22.3 (2.16.1), 14.23.1 (2.17.0), 15.10.8 (3.8.4), 15.12.8 (3.9.4), 15.13.6 (3.10.3), 15.14.5 (3.11.2), 15.15.5 (3.12.2), 15.17.3 (3.13.1), 15.18.1 (3.14.0), 16.8.8 (4.5.5), 16.9.6 (4.6.3), 16.10.5 (4.7.2), 16.11.5 (4.8.2), 16.13.3 (4.9.1), 16.14.1 (4.10.0), 17.4.8 (5.1.4), 17.5.6 (5.2.3), 17.6.5 (5.3.2), 17.7.5 (5.4.2), 17.9.3 (5.5.1), 17.10.1 (5.6.0), 18.3.4 (6.0.2), 18.4.1 (6.1.0) or later, and apply any pending maintenance to ensure they are on the latest patch.

Severity

CVSS 4.0

7.2 high

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

8.1 high

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

EPSS: 0.5% estimated probability of exploitation activity in the next 30 days; 45th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC): Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE: CWE-125 Out-of-bounds Read
Published: 2026-11-06 19:17 UTC
Modified: 2026-11-12 19:24 UTC
NVD analysis: Awaiting analysis
Record from: the NVD, synced 2026-11-12 19:53 UTC

Ask an AI about this CVE

ChatGPT Claude Google AI Mode

Show the prompt

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

Badge for a README or a site

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-119924](https://cve.bz/cve/badge/CVE-2026-119924.svg)](https://cve.bz/cve/CVE-2026-119924)

HTML:

<a href="https://cve.bz/cve/CVE-2026-119924"><img src="https://cve.bz/cve/badge/CVE-2026-119924.svg" alt="CVE-2026-119924"></a>

Affected

amazon:amazon aurora postgresql with babelfish
aws:babelfish-for-postgresql

Versions

From the CNA's record in the CVE List.

Product	Affected
AWS babelfish-for-postgresql	from 1.0 through 1.5
AWS babelfish-for-postgresql	from 2.1 through 2.15
AWS babelfish-for-postgresql	from 3.1 through 3.12
AWS babelfish-for-postgresql	from 4.0 through 4.8
AWS babelfish-for-postgresql	from 5.1 through 5.4
Amazon Aurora PostgreSQL with Babelfish	from 1.0.0 before 1.5.5
Amazon Aurora PostgreSQL with Babelfish	from 1.6.0 before 1.17.2
Amazon Aurora PostgreSQL with Babelfish	from 2.0.0 before 2.3.5
Amazon Aurora PostgreSQL with Babelfish	from 2.4.0 before 2.12.4
Amazon Aurora PostgreSQL with Babelfish	from 2.13.0 before 2.13.3
Amazon Aurora PostgreSQL with Babelfish	from 2.14.0 before 2.14.2
Amazon Aurora PostgreSQL with Babelfish	from 2.15.0 before 2.15.2
Amazon Aurora PostgreSQL with Babelfish	from 2.16.0 before 2.16.1
Amazon Aurora PostgreSQL with Babelfish	from 3.0.0 before 3.8.4
Amazon Aurora PostgreSQL with Babelfish	from 3.9.0 before 3.9.4
Amazon Aurora PostgreSQL with Babelfish	from 3.10.0 before 3.10.3
Amazon Aurora PostgreSQL with Babelfish	from 3.11.0 before 3.11.2
Amazon Aurora PostgreSQL with Babelfish	from 3.12.0 before 3.12.2
Amazon Aurora PostgreSQL with Babelfish	from 3.13.0 before 3.13.1
Amazon Aurora PostgreSQL with Babelfish	from 4.0.0 before 4.5.5
Amazon Aurora PostgreSQL with Babelfish	from 4.6.0 before 4.6.3
Amazon Aurora PostgreSQL with Babelfish	from 4.7.0 before 4.7.2
Amazon Aurora PostgreSQL with Babelfish	from 4.8.0 before 4.8.2
Amazon Aurora PostgreSQL with Babelfish	from 4.9.0 before 4.9.1
Amazon Aurora PostgreSQL with Babelfish	from 5.0.0 before 5.1.4
Amazon Aurora PostgreSQL with Babelfish	from 5.2.0 before 5.2.3
Amazon Aurora PostgreSQL with Babelfish	from 5.3.0 before 5.3.2
Amazon Aurora PostgreSQL with Babelfish	from 5.4.0 before 5.4.2
Amazon Aurora PostgreSQL with Babelfish	5.5.0
Amazon Aurora PostgreSQL with Babelfish	from 6.0.0 before 6.0.2

Attack patterns (CAPEC)

CAPEC-540 Overread Buffers Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stack JSON