HighCVE-2026-119924

    Out-of-Bounds Read in Babelfish for PostgreSQL TDS RPC Procedure-Name Parser (CVE-2026-119924)

    Published Last modified Sources: pwn.watch, CVE.org

    Share

    What is affected, what to do

    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.

    Update Amazon Aurora PostgreSQL with Babelfish to version 1.5.5, Amazon Aurora PostgreSQL with Babelfish to version 1.17.2, Amazon Aurora PostgreSQL with Babelfish to version 2.3.5.

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

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    8.1

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    8.1

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: pwn.watch, CVE.org

    —

    EPSS score

    No value is available for this vulnerability.

    Show all metrics
    Severity
    High
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    70.50 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    8.1 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    8.1
    CVSS v4

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.2
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: none known · not automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 6 November 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-125

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    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.

    Source: pwn.watch, cvelistv5, NVD (NIST)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    AmazonAmazon Aurora PostgreSQL with Babelfish
    • 5.4.0 – < 5.4.2
    • 3.13.0 – < 3.13.1
    • 2.14.0 – < 2.14.2
    • 2.4.0 – < 2.12.4
    • 2.0.0 – < 2.3.5
    • 5.0.0 – < 5.1.4
    • 4.7.0 – < 4.7.2
    • 4.6.0 – < 4.6.3
    • 2.15.0 – < 2.15.2
    • 4.0.0 – < 4.5.5
    • 3.10.0 – < 3.10.3
    • 2.16.0 – < 2.16.1
    • 6.0.0 – < 6.0.2
    • 3.9.0 – < 3.9.4
    • 5.2.0 – < 5.2.3
    • 2.13.0 – < 2.13.3
    • 1.6.0 – < 1.17.2
    • 5.3.0 – < 5.3.2
    • 1.0.0 – < 1.5.5
    • 4.8.0 – < 4.8.2
    • 5.5.0
    • 3.12.0 – < 3.12.2
    • 3.11.0 – < 3.11.2
    • 3.0.0 – < 3.8.4
    • 4.9.0 – < 4.9.1
    • 5.4.2
    • 3.13.1
    • 2.14.2
    • 2.12.4
    • 2.3.5
    • 5.1.4
    • 4.7.2
    • 4.6.3
    • 2.15.2
    • 4.5.5
    • 3.10.3
    • 2.16.1
    • 6.0.2
    • 3.9.4
    • 5.2.3
    • 2.13.3
    • 1.17.2
    • 5.3.2
    • 1.5.5
    • 4.8.2
    • —
    • 3.12.2
    • 3.11.2
    • 3.8.4
    • 4.9.1
    AWSbabelfish-for-postgresql
    • 3.1 – ≤ 3.12
    • 5.1 – ≤ 5.4
    • 1.0 – ≤ 1.5
    • 2.1 – ≤ 2.15
    • 4.0 – ≤ 4.8
    • —
    • —
    • —
    • —
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-125Out-of-bounds Read

      Base

      The product reads data past the end, or before the beginning, of the intended buffer.

      Entry at MITRE CWE-125

    References & sources

    • aws.amazon.comCVE-2026-119923 and CVE-2026-119924: Issues with Babelfish for Aurora PostgreSQL (2026-166-AWS)pwn-watch, Vendor advisory
    • github.combabelfish-for-postgresql/babelfish-for-postgresql/releases/tag/…Release notes, Patch
    • github.combabelfish-for-postgresql/babelfish-for-postgresql/releases/tag/…Release notes, Patch
    • github.combabelfish-for-postgresql/babelfish-for-postgresql/releases/tag/…Release notes, Patch
    • pwn.watchpwn.watch: AWS Babelfish for Aurora PostgreSQL TDS parser issues (CVE-2026-119923, CVE-2026-119924)pwn-watch
    • NVD (NIST)NVD CVE-2026-119923pwn-watch
    • NVD (NIST)NVD CVE-2026-119924pwn-watch

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: none known, automatable: no

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentadded
      —
      {"id":"CVE-2026-119924","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-11-06T20:21:08.740024Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    2. ReceivedAmazon

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

      CVSS V3.1: AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

      Weakness type: CWE-125

      Description added or changed

      Show 9 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      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.
      CVSSadded
      —
      AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
      CVSSadded
      —
      AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
      Weakness type (CWE)added
      —
      CWE-125
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/119xxx/CVE-2026-119924.json">CVE-2026-119924</a>
      Referenceadded
      —
      https://aws.amazon.com/security/security-bulletins/2026-166-aws/
      Referenceadded
      —
      https://github.com/babelfish-for-postgresql/babelfish-for-postgresql/releases/tag/BABEL_4_10_0__PG_16_14
      Referenceadded
      —
      https://github.com/babelfish-for-postgresql/babelfish-for-postgresql/releases/tag/BABEL_5_6_0__PG_17_10
      Referenceadded
      —
      https://github.com/babelfish-for-postgresql/babelfish-for-postgresql/releases/tag/BABEL_6_1_0__PG_18_4

      Source identifier: ff89ba41-3aa1-4d27-914a-91399e9639e5

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-119924
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-119924"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-119924.svg?lang=en" alt="CVE-2026-119924 – NEOSEC Intel" height="20"></a>