Skip to content
CVE-2026-119923: Match Babelfish and Aurora patch targets

CVE-2026-119923: Match Babelfish and Aurora patch targets

November 19, 2026

AWS published CVE-2026-119923 on November 6, 2026. Amazon’s CVE Program record rates it Critical under both CVSS 3.1 (9.8) and CVSS 4.0 (9.3).

Standalone Babelfish

AWS lists affected extension ranges 1.0 through 1.5, 2.1 through 2.15, 3.1 through 3.12, 4.0 through 4.8, and 5.1 through 5.4. Its remediation targets are Babelfish 4.10, 5.6, or 6.1 or later, following the appropriate supported upgrade path.

Record both PostgreSQL and Babelfish versions before selecting a target. Verify compatibility, backups and recovery procedures before maintenance. Complete the extension upgrade as well as the software deployment, then confirm the installed extension version.

Aurora PostgreSQL with Babelfish

Use AWS’s Aurora-specific mapping. Standalone version thresholds do not replace managed-service patch instructions. Examples from the advisory include:

Aurora PostgreSQL patchIncluded Babelfish version
16.8.84.5.5
16.14.14.10.0
17.4.85.1.4
17.10.15.6.0
18.3.46.0.2
18.4.16.1.0

These are examples, not the complete branch list. Match the cluster’s existing engine branch to the full AWS advisory and apply pending maintenance. Do not infer that a numerically older included Babelfish version is unpatched when AWS explicitly lists that Aurora build as corrected.

Verify completed maintenance

For managed clusters, record the actual engine version after the maintenance completes, together with the selected target and maintenance status. A scheduled update is still outstanding work.

Check ordinary authorized application connections and a small application-owned read/write transaction after maintenance. Use a designated test record and remove it afterward. Record failures for investigation; routine functionality checks do not establish absence of compromise.

Acknowledgements

This post was created with assistance from AI.

Last updated on