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

Published Nov 6, 2026
·
Updated

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.

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Babelfish for PostgreSQL extension to a version that resolves this vulnerability.

    Fixed in 4.10
  2. Upgrade

    Upgrade Babelfish for PostgreSQL extension to a version that resolves this vulnerability.

    Fixed in 5.6
  3. Upgrade

    Upgrade Babelfish for PostgreSQL extension to a version that resolves this vulnerability.

    Fixed in 6.1
  4. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 13.9.16 (1.5.5)
  5. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 13.23.3 (1.17.2)
  6. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 14.6.16 (2.3.5)
  7. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 14.17.8 (2.12.4)
  8. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 14.18.6 (2.13.3)
  9. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 14.19.5 (2.14.2)
  10. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 14.20.5 (2.15.2)
  11. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 14.22.3 (2.16.1)
  12. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 14.23.1 (2.17.0)
  13. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 15.10.8 (3.8.4)
  14. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 15.12.8 (3.9.4)
  15. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 15.13.6 (3.10.3)
  16. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 15.14.5 (3.11.2)
  17. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 15.15.5 (3.12.2)
  18. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 15.17.3 (3.13.1)
  19. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 15.18.1 (3.14.0)
  20. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 16.8.8 (4.5.5)
  21. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 16.9.6 (4.6.3)
  22. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 16.10.5 (4.7.2)
  23. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 16.11.5 (4.8.2)
  24. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 16.13.3 (4.9.1)
  25. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 16.14.1 (4.10.0)
  26. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 17.4.8 (5.1.4)
  27. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 17.5.6 (5.2.3)
  28. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 17.6.5 (5.3.2)
  29. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 17.7.5 (5.4.2)
  30. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 17.9.3 (5.5.1)
  31. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 17.10.1 (5.6.0)
  32. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 18.3.4 (6.0.2)
  33. Upgrade

    Upgrade Amazon Aurora PostgreSQL with Babelfish to a version that resolves this vulnerability.

    Fixed in 18.4.1 (6.1.0)
  34. Compensating control

    Restrict network access to the TDS port (default 1433).

Event History

Nov 6, 2026
CVE Published
via MITRE·06:38 PM
Data Sourced
via MITRE·06:38 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:17 PM
DescriptionSeverityWeakness

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203