AWS Security ChangesHomeSearch

AWS AmazonRDS: Aurora PostgreSQL release notes add 13.23.6–17.7.6 with CVE fixes

Service: AmazonRDS · 2026-10-29 · Security-related high

File: AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/AuroraPostgreSQL.Updates.md · Type: vulnerability-patching · CVE: CVE-2026-6464, CVE-2026-6469, CVE-2026-6470, CVE-2026-6471, CVE-2026-14662, CVE-2026-14663, CVE-2026-14664, CVE-2026-14666, CVE-2026-14668, CVE-2026-14669, CVE-2026-14670, CVE-2026-14671, CVE-2026-14672, CVE-2026-14673, CVE-2026-14677, CVE-2026-14678, CVE-2026-14679, CVE-2026-14680, CVE-2026-14681, CVE-2026-15741, CVE-2026-15742, CVE-2026-16239, CVE-2026-16241, CVE-2026-18024, CVE-2026-18408

Summary

Adds release-note entries for Aurora PostgreSQL versions 17.7.6, 16.11.6, 15.15.6, 14.20.6, and 13.23.6 (October 30, 2026), each listing critical stability fixes (storage metadata startup failure at max volume size, HypoPG EXPLAIN role scoping, index scan prefetch duplicate rows), a 'High priority enhancements' section enumerating backported PostgreSQL community security fixes with CVE links, and general enhancements (replica stability, Aurora Storage Daemon memory/logging fixes, tzdata 2026c).

Security assessment

The added sections explicitly state that these engine releases backport fixes for named PostgreSQL community security issues and link each CVE, so the change documents remediation of concrete vulnerabilities across five Aurora PostgreSQL major versions. It is release-note disclosure of patched CVEs rather than documentation of a security feature or best practice, hence adds_security_documentation is false. Severity is high because it concerns fixed vulnerabilities/CVEs in the database engine.

Evidence

+  * Backported fixes for the following PostgreSQL community security issues:

Diff

diff --git a/AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/AuroraPostgreSQL.Updates.md b/AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/AuroraPostgreSQL.Updates.md
index d299e09..d38ff4a 100644
--- a//AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/AuroraPostgreSQL.Updates.md
+++ b//AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/AuroraPostgreSQL.Updates.md
@@ -1395,0 +1396,2 @@ This release of Aurora PostgreSQL is compatible with PostgreSQL 17.7. For more i
+  * Aurora PostgreSQL 17.7.6, October 30, 2026
+
@@ -1410,0 +1413,85 @@ This release of Aurora PostgreSQL is compatible with PostgreSQL 17.7. For more i
+#### Aurora PostgreSQL 17.7.6, October 30, 2026
+
+**Critical stability enhancements**
+
+  * Fixed an issue in Aurora storage metadata that can cause a database to become unable to start up when hitting the maximum storage volume size.
+
+  * HypoPG will only consider hypothetical indexes during EXPLAIN that were created by the current role.
+
+  * Fixed an issue with index scan prefetch that could return duplicate rows, and increased I/O wait times.
+
+
+
+
+**High priority enhancements**
+
+  * Backported fixes for the following PostgreSQL community security issues:
+
+    * [CVE-2026-6464](https://www.postgresql.org/support/security/CVE-2026-6464)
+
+    * [CVE-2026-6469](https://www.postgresql.org/support/security/CVE-2026-6469)
+
+    * [CVE-2026-6470](https://www.postgresql.org/support/security/CVE-2026-6470)
+
+    * [CVE-2026-6471](https://www.postgresql.org/support/security/CVE-2026-6471)
+
+    * [CVE-2026-14662](https://www.postgresql.org/support/security/CVE-2026-14662)
+
+    * [CVE-2026-14663](https://www.postgresql.org/support/security/CVE-2026-14663)
+
+    * [CVE-2026-14664](https://www.postgresql.org/support/security/CVE-2026-14664)
+
+    * [CVE-2026-14666](https://www.postgresql.org/support/security/CVE-2026-14666)
+
+    * [CVE-2026-14668](https://www.postgresql.org/support/security/CVE-2026-14668)
+
+    * [CVE-2026-14669](https://www.postgresql.org/support/security/CVE-2026-14669)
+
+    * [CVE-2026-14670](https://www.postgresql.org/support/security/CVE-2026-14670)
+
+    * [CVE-2026-14671](https://www.postgresql.org/support/security/CVE-2026-14671)
+
+    * [CVE-2026-14672](https://www.postgresql.org/support/security/CVE-2026-14672)
+
+    * [CVE-2026-14673](https://www.postgresql.org/support/security/CVE-2026-14673)
+
+    * [CVE-2026-14677](https://www.postgresql.org/support/security/CVE-2026-14677)
+
+    * [CVE-2026-14678](https://www.postgresql.org/support/security/CVE-2026-14678)
+
+    * [CVE-2026-14679](https://www.postgresql.org/support/security/CVE-2026-14679)
+
+    * [CVE-2026-14680](https://www.postgresql.org/support/security/CVE-2026-14680)
+
+    * [CVE-2026-14681](https://www.postgresql.org/support/security/CVE-2026-14681)
+
+    * [CVE-2026-15741](https://www.postgresql.org/support/security/CVE-2026-15741)
+
+    * [CVE-2026-15742](https://www.postgresql.org/support/security/CVE-2026-15742)
+
+    * [CVE-2026-16239](https://www.postgresql.org/support/security/CVE-2026-16239)
+
+    * [CVE-2026-16241](https://www.postgresql.org/support/security/CVE-2026-16241)
+
+    * [CVE-2026-18024](https://www.postgresql.org/support/security/CVE-2026-18024)
+
+    * [CVE-2026-18408](https://www.postgresql.org/support/security/CVE-2026-18408)
+
+
+
+
+**General enhancements**
+
+  * Fixed an issue with reader instances, improving replica stability.
+
+  * Fixed an issue that can cause a database instance to restart due to a memory management issue in connection handling of the Aurora Storage Daemon.
+
+  * Fixed increased storage consumption by internal logging of the Aurora Storage Daemon.
+
+  * Fixed an issue that can cause the database to restart when a storage configuration change occurs while a metadata synchronization operation is still in progress.
+
+  * Updated time zone data files to tzdata release 2026c.
+
+
+
+
@@ -3350,0 +3438,2 @@ This release of Aurora PostgreSQL is compatible with PostgreSQL 16.11. For more
+  * Aurora PostgreSQL 16.11.6, October 30, 2026
+
@@ -3365,0 +3455,83 @@ This release of Aurora PostgreSQL is compatible with PostgreSQL 16.11. For more
+#### Aurora PostgreSQL 16.11.6, October 30, 2026
+
+**Critical stability enhancements**
+
+  * Fixed an issue in Aurora storage metadata that can cause a database to become unable to start up when hitting the maximum storage volume size.
+
+  * HypoPG will only consider hypothetical indexes during EXPLAIN that were created by the current role.
+
+  * Fixed an issue with index scan prefetch that could return duplicate rows, and increased I/O wait times.
+
+
+
+
+**High priority enhancements**
+
+  * Backported fixes for the following PostgreSQL community security issues:
+
+    * [CVE-2026-6464](https://www.postgresql.org/support/security/CVE-2026-6464)
+
+    * [CVE-2026-6469](https://www.postgresql.org/support/security/CVE-2026-6469)
+
+    * [CVE-2026-6470](https://www.postgresql.org/support/security/CVE-2026-6470)
+
+    * [CVE-2026-6471](https://www.postgresql.org/support/security/CVE-2026-6471)
+
+    * [CVE-2026-14662](https://www.postgresql.org/support/security/CVE-2026-14662)
+
+    * [CVE-2026-14663](https://www.postgresql.org/support/security/CVE-2026-14663)
+
+    * [CVE-2026-14664](https://www.postgresql.org/support/security/CVE-2026-14664)
+
+    * [CVE-2026-14666](https://www.postgresql.org/support/security/CVE-2026-14666)
+
+    * [CVE-2026-14668](https://www.postgresql.org/support/security/CVE-2026-14668)
+
+    * [CVE-2026-14669](https://www.postgresql.org/support/security/CVE-2026-14669)
+
+    * [CVE-2026-14670](https://www.postgresql.org/support/security/CVE-2026-14670)
+
+    * [CVE-2026-14671](https://www.postgresql.org/support/security/CVE-2026-14671)
+
+    * [CVE-2026-14672](https://www.postgresql.org/support/security/CVE-2026-14672)
+
+    * [CVE-2026-14673](https://www.postgresql.org/support/security/CVE-2026-14673)
+
+    * [CVE-2026-14677](https://www.postgresql.org/support/security/CVE-2026-14677)
+
+    * [CVE-2026-14678](https://www.postgresql.org/support/security/CVE-2026-14678)
+
+    * [CVE-2026-14679](https://www.postgresql.org/support/security/CVE-2026-14679)
+
+    * [CVE-2026-14680](https://www.postgresql.org/support/security/CVE-2026-14680)
+
+    * [CVE-2026-15741](https://www.postgresql.org/support/security/CVE-2026-15741)
+
+    * [CVE-2026-15742](https://www.postgresql.org/support/security/CVE-2026-15742)
+
+    * [CVE-2026-16239](https://www.postgresql.org/support/security/CVE-2026-16239)
+
+    * [CVE-2026-16241](https://www.postgresql.org/support/security/CVE-2026-16241)
+
+    * [CVE-2026-18024](https://www.postgresql.org/support/security/CVE-2026-18024)
+
+    * [CVE-2026-18408](https://www.postgresql.org/support/security/CVE-2026-18408)
+
+
+
+
+**General enhancements**
+
+  * Fixed an issue with reader instances, improving replica stability.
+
+  * Fixed an issue that can cause a database instance to restart due to a memory management issue in connection handling of the Aurora Storage Daemon.
+
+  * Fixed increased storage consumption by internal logging of the Aurora Storage Daemon.
+
+  * Fixed an issue that can cause the database to restart when a storage configuration change occurs while a metadata synchronization operation is still in progress.
+
+  * Updated time zone data files to tzdata release 2026c.
+
+
+
+
@@ -6490,0 +6663,2 @@ This release of Aurora PostgreSQL is compatible with PostgreSQL 15.15. For more
+  * Aurora PostgreSQL 15.15.6, October 30, 2026
+
@@ -6505,0 +6680,81 @@ This release of Aurora PostgreSQL is compatible with PostgreSQL 15.15. For more
+#### Aurora PostgreSQL 15.15.6, October 30, 2026
+
+**Critical stability enhancements**
+
+  * Fixed an issue in Aurora storage metadata that can cause a database to become unable to start up when hitting the maximum storage volume size.
+
+  * HypoPG will only consider hypothetical indexes during EXPLAIN that were created by the current role.
+
+  * Fixed an issue with index scan prefetch that could return duplicate rows, and increased I/O wait times.
+
+
+
+
+**High priority enhancements**
+
+  * Backported fixes for the following PostgreSQL community security issues: