Remote code execution in Babelfish affecting Amazon Aurora PostgreSQL (widely used cloud DB). Network-exploitable RCE against managed/cloud DB services merits broad IT/security notification.
CVE-2026-119923
RCE in Babelfish prelogin parser via malformed TDS packet.
Is CVE-2026-119923 being exploited?
Not confirmed. CVE-2026-119923 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.
How severe is CVE-2026-119923?
CVE-2026-119923 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-119923?
Yes. A fix has been recorded for CVE-2026-119923. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-119923 affect?
CVE-2026-119923 affects Babelfish for PostgreSQL (v1.0-1.5,2.1-2.15,3.1-3.12,4.0-4.8,5.1-5.4), Amazon Aurora PostgreSQL with Babelfish (multiple affected versions; see advisory). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-119923?
Upgrade Babelfish/Aurora to vendor fixed versions or block TDS (1433) until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution as the database process user via malformed TDS prelogin packet to the TDS port (default 1433).
Immediate action required
- affected>= 1.0.0 and < 1.5.5
- affected>= 1.6.0 and < 1.17.2
- affected>= 2.0.0 and < 2.3.5
- affected>= 2.4.0 and < 2.12.4
- affected>= 2.13.0 and < 2.13.3
- affected>= 2.14.0 and < 2.14.2
- affected>= 2.15.0 and < 2.15.2
- affected>= 2.16.0 and < 2.16.1
- affected>= 3.0.0 and < 3.8.4
- affected>= 3.9.0 and < 3.9.4
- affected>= 3.10.0 and < 3.10.3
- affected>= 3.11.0 and < 3.11.2
- affected>= 3.12.0 and < 3.12.2
- affected>= 3.13.0 and < 3.13.1
- affected>= 4.0.0 and < 4.5.5
- affected>= 4.6.0 and < 4.6.3
- affected>= 4.7.0 and < 4.7.2
- affected>= 4.8.0 and < 4.8.2
- affected>= 4.9.0 and < 4.9.1
- affected>= 5.0.0 and < 5.1.4
- affected>= 5.2.0 and < 5.2.3
- affected>= 5.3.0 and < 5.3.2
- affected>= 5.4.0 and < 5.4.2
- affected5.5.0
- affected>= 6.0.0 and < 6.0.2
- affected>= 1.0 and <= 1.5
- affected>= 2.1 and <= 2.15
- affected>= 3.1 and <= 3.12
- affected>= 4.0 and <= 4.8
- affected>= 5.1 and <= 5.4
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- none
- automatable
- yes
- technical impact
- total
Assessed by CISA 6 Nov 2026 (SSVC 2.0.3).
timeline
- 6 Nov 2026Published
- 6 Nov 2026CISA SSVC assessment: exploitation none · same day later
- 6 Nov 2026CVE record last updated · same day later
- 7 Nov 2026Analysed by vulneraibility.com · 1 day later
- Advisoryaws.amazon.com /security/security-bulletins/2026-166-aws/
- Patchgithub.com /babelfish-for-postgresql/babelfish-for-postgresql/releases/tag/BABEL_4_10_0__PG
- Patchgithub.com /babelfish-for-postgresql/babelfish-for-postgresql/releases/tag/BABEL_5_6_0__PG_
- Patchgithub.com /babelfish-for-postgresql/babelfish-for-postgresql/releases/tag/BABEL_6_1_0__PG_
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.