Is CVE-2026-119923 exploited in the wild?

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

How severe is CVE-2026-119923?

Critical severity, with a CVSS score of 9.8, published 6 November 2026.

Which products and versions are affected?

AWS Aurora PostgreSQL with Babelfish Aurora PostgreSQL 13.x with Babelfish 1.x ( =1.6.0 and <1.17.2), 14.x with Babelfish 2.x (affected versions), 15.x with Babelfish 3.x (affected versions), 16.x with Babelfish 4.x (affected versions), 17.x with Babelfish 5.x (affected versions), 18.x with Babelfish 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-119923?

Yes: fixed in Babelfish for PostgreSQL extension 4.10, 5.6, 6.1 or later; Aurora PostgreSQL versions: 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 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-119923 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-119923?

Check whether you run Amazon AWS, 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-119923: Babelfish for PostgreSQL heap-based buffer overflow in TDS prelogin parser

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

Yes: fixed in Babelfish for PostgreSQL extension 4.10, 5.6, 6.1 or later; Aurora PostgreSQL versions: 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 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-119923 attacked?

It is attacked over the network, in a software library.

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

Check whether you run Amazon AWS, 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-119923 · Severity: critical · CVSS 9.8 · Published 2026-11-06

Babelfish is a PostgreSQL extension that allows applications built for SQL Server to connect without modifying application code. A heap-based buffer overflow in the TDS prelogin parser allows remote, unauthenticated attackers to execute arbitrary commands as the database process user by sending a specially crafted malformed TDS prelogin packet. This could lead to complete database compromise, including data theft, modification, or service outage.

Technologies: Amazon AWS, AWS Babelfish for PostgreSQL. Vendors: Amazon, AWS.

Quick answers

Is CVE-2026-119923 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-119923 being exploited in the wild.
How severe is CVE-2026-119923?: Critical severity, with a CVSS score of 9.8, published 6 November 2026.
Which products and versions are affected?: AWS Aurora PostgreSQL with Babelfish Aurora PostgreSQL 13.x with Babelfish 1.x (<1.5.5 or >=1.6.0 and <1.17.2), 14.x with Babelfish 2.x (affected versions), 15.x with Babelfish 3.x (affected versions), 16.x with Babelfish 4.x (affected versions), 17.x with Babelfish 5.x (affected versions), 18.x with Babelfish 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-119923?: Yes: fixed in Babelfish for PostgreSQL extension 4.10, 5.6, 6.1 or later; Aurora PostgreSQL versions: 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 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-119923 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-119923?: Check whether you run Amazon AWS, 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 4.10, 5.6, 6.1 or later; Aurora PostgreSQL versions: 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 until the upgrade is applied.

Technical details

A heap-based buffer overflow exists in the TDS prelogin parser component of Babelfish, exploitable before authentication via a malformed TDS prelogin packet sent to the TDS port (default 1433). The vulnerability also includes a related NULL-pointer-dereference finding in the same parser. Successful exploitation allows unauthenticated remote code execution as the PostgreSQL process user, affecting confidentiality, integrity, and availability of the database.

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 Aurora PostgreSQL 13.x with Babelfish 1.x (<1.5.5 or >=1.6.0 and <1.17.2), 14.x with Babelfish 2.x (affected versions), 15.x with Babelfish 3.x (affected versions), 16.x with Babelfish 4.x (affected versions), 17.x with Babelfish 5.x (affected versions), 18.x with Babelfish 6.x (<6.0.2)

Identifiers

CVE-2026-119923
CVE-2026-119924

Timeline

2026-11-06: disclosed
2026-11-02: patched: Babelfish 4.10.0 released on GitHub

References

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