Is CVE-2026-119924 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-119924 being exploited in the wild.

How severe is CVE-2026-119924?

High severity, with a CVSS score of 8.1, published 6 November 2026.

Which products and versions are affected?

AWS Aurora PostgreSQL with Babelfish 1.x ( =1.6.0 <1.17.2), 2.x (multiple ranges), 3.x (multiple ranges), 4.x (multiple ranges), 5.x (multiple ranges), 6.x (<6.0.2); AWS Babelfish for PostgreSQL 1.0-1.5, 2.1-2.15, 3.1-3.12, 4.0-4.8, 5.1-5.4.

Is there a fix for CVE-2026-119924?

Yes: fixed in Babelfish for PostgreSQL extension versions 4.10, 5.6, 6.1 or later; Amazon 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. Until then: Restrict network access to the TDS port (default 1433) to trusted sources using VPC security groups or firewall rules until the upgrade is applied. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-119924 attacked?

It is attacked over the network.

Am I affected by CVE-2026-119924?

Check whether you run AWS Aurora PostgreSQL with Babelfish or AWS Babelfish for PostgreSQL at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-119924: Babelfish for PostgreSQL out-of-bounds read in TDS RPC parser

Q: Is there a fix for CVE-2026-119924?

Yes: fixed in Babelfish for PostgreSQL extension versions 4.10, 5.6, 6.1 or later; Amazon 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. Until then: Restrict network access to the TDS port (default 1433) to trusted sources using VPC security groups or firewall rules until the upgrade is applied. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-119924 attacked?

It is attacked over the network.

Q: Am I affected by CVE-2026-119924?

Check whether you run AWS Aurora PostgreSQL with Babelfish or AWS Babelfish for PostgreSQL at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-119924 · Severity: high · CVSS 8.1 · Published 2026-11-06

Babelfish for PostgreSQL is an extension that allows PostgreSQL to understand SQL Server's wire protocol, enabling SQL Server applications to run without modification. An out-of-bounds memory read flaw in the TDS RPC (remote procedure call) parser allows authenticated attackers to read sensitive data from the database process memory or crash the database via a malformed RPC request, affecting availability and confidentiality.

Technologies: AWS Babelfish for PostgreSQL. Vendors: AWS.

Quick answers

Is CVE-2026-119924 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-119924 being exploited in the wild.
How severe is CVE-2026-119924?: High severity, with a CVSS score of 8.1, published 6 November 2026.
Which products and versions are affected?: AWS Aurora PostgreSQL with Babelfish 1.x (<1.5.5, >=1.6.0 <1.17.2), 2.x (multiple ranges), 3.x (multiple ranges), 4.x (multiple ranges), 5.x (multiple ranges), 6.x (<6.0.2); AWS Babelfish for PostgreSQL 1.0-1.5, 2.1-2.15, 3.1-3.12, 4.0-4.8, 5.1-5.4.
Is there a fix for CVE-2026-119924?: Yes: fixed in Babelfish for PostgreSQL extension versions 4.10, 5.6, 6.1 or later; Amazon 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. Until then: Restrict network access to the TDS port (default 1433) to trusted sources using VPC security groups or firewall rules until the upgrade is applied. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-119924 attacked?: It is attacked over the network.
Am I affected by CVE-2026-119924?: Check whether you run AWS Aurora PostgreSQL with Babelfish or AWS Babelfish for PostgreSQL at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: Babelfish for PostgreSQL extension versions 4.10, 5.6, 6.1 or later; Amazon 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

Restrict network access to the TDS port (default 1433) to trusted sources using VPC security groups or firewall rules until the upgrade is applied.

Technical details

An out-of-bounds read vulnerability exists in the TDS RPC procedure-name parser when processing malformed TDS RPC requests. Remote authenticated users can exploit this via the TDS port (default 1433) to read adjacent process memory or trigger a denial of service. The vulnerability affects Babelfish extension versions 1.0–1.5, 2.1–2.15, 3.1–3.12, 4.0–4.8, and 5.1–5.4, as well as Amazon Aurora PostgreSQL with Babelfish.

Affected products

AWS Babelfish for PostgreSQL 1.0-1.5, 2.1-2.15, 3.1-3.12, 4.0-4.8, 5.1-5.4
AWS Aurora PostgreSQL with Babelfish 1.x (<1.5.5, >=1.6.0 <1.17.2), 2.x (multiple ranges), 3.x (multiple ranges), 4.x (multiple ranges), 5.x (multiple ranges), 6.x (<6.0.2)

Timeline

2026-11-06: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.