---
title: "CVE-2026-119923: Babelfish for PostgreSQL - Buffer Overflow"
description: "Babelfish for PostgreSQL extension 1.0-1.5, 2.1-2.15, 3.1-3.12, 4.0-4.8, 5.1-5.4 and Amazon Aurora PostgreSQL with Babelfish contain a heap-based buffer overflow caused by improper handling in the TDS prelogin parser, letting remote attackers execute arbitrary OS commands as the database process user via malformed TDS prelogin packets, exploit requires network access to TDS port."
url: https://panop.io/threat-heartbeat/CVE-2026-119923/
---

# CVE-2026-119923 Babelfish for PostgreSQL - Buffer Overflow

Babelfish for PostgreSQL extension 1.0-1.5, 2.1-2.15, 3.1-3.12, 4.0-4.8, 5.1-5.4 and Amazon Aurora PostgreSQL with Babelfish contain a heap-based buffer overflow caused by improper handling in the TDS prelogin parser, letting remote attackers execute arbitrary OS commands as the database process user via malformed TDS prelogin packets, exploit requires network access to TDS port.

CVSS base score 9.8 /10

Critical

CISA KEV

Not listed

Public exploit

None known

EPSS

0.62% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-119923)

## Details

Type

Buffer Overflow

Impact

Remote Code Execution

CVSS vector

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

Published

6 November 2026

Updated

9 November 2026

Weakness

[CWE-122](https://cwe.mitre.org/data/definitions/122.html)

## Vendor fix

Upgrade to Babelfish for PostgreSQL extension versions 4.10, 5.6, 6.1 or later; Amazon Aurora PostgreSQL clusters should upgrade to the specified patched versions or later.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-119923](https://nvd.nist.gov/vuln/detail/CVE-2026-119923)
- [https://aws.amazon.com/security/security-bulletins/2026-166-aws/](https://aws.amazon.com/security/security-bulletins/2026-166-aws/)
- [https://github.com/babelfish-for-postgresql/babelfish-for-postgresql/releases/tag/BABEL\_4\_10\_0\_\_PG\_16\_14](https://github.com/babelfish-for-postgresql/babelfish-for-postgresql/releases/tag/BABEL_4_10_0__PG_16_14)
- [https://github.com/babelfish-for-postgresql/babelfish-for-postgresql/releases/tag/BABEL\_5\_6\_0\_\_PG\_17\_10](https://github.com/babelfish-for-postgresql/babelfish-for-postgresql/releases/tag/BABEL_5_6_0__PG_17_10)
- [https://github.com/babelfish-for-postgresql/babelfish-for-postgresql/releases/tag/BABEL\_6\_1\_0\_\_PG\_18\_4](https://github.com/babelfish-for-postgresql/babelfish-for-postgresql/releases/tag/BABEL_6_1_0__PG_18_4)
- [https://github.com/babelfish-for-postgresql/babelfish\_extensions/security/advisories/GHSA-vq28-vgj3-r26w](https://github.com/babelfish-for-postgresql/babelfish_extensions/security/advisories/GHSA-vq28-vgj3-r26w)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)
