Amazon RDS for PostgreSQL 9.6 · Version Status

Amazon RDS for PostgreSQL 9.6 End of Life Date

Amazon RDS for PostgreSQL 9.6 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Amazon RDS for PostgreSQL 9.6 is past end of life. This version no longer receives security patches. 1564 days past EOL — migrate to a supported version immediately.
EOL Date
Apr 30, 2022
1564 days past EOL
Latest Release
9.6.24
Standard release
Release Date
Nov 11, 2016
Amazon RDS for PostgreSQL 9.6 series
Lifecycle detail

Amazon RDS for PostgreSQL 9.6 was released on November 11, 2016 and support ended on April 30, 2022 — a supported lifespan of 5 years and 6 months, in line with the 5 years and 2 months median for Amazon RDS for PostgreSQL releases. The last patch it will ever receive is 9.6.24, published January 24, 2022 — 3 months before support ended. It has been without security patches for 4 years and 3 months. 4 newer Amazon RDS for PostgreSQL releases have shipped since.

All Amazon RDS for PostgreSQL versions Amazon RDS for PostgreSQL 10 →
50 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
40/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →  ·  View score card →
Recommended upgrade path
Amazon RDS for PostgreSQL 18
Latest release: 18.4 · EOL: Feb 28, 2031
View full Amazon RDS for PostgreSQL timeline →
Extended Support
Extended Amazon RDS for PostgreSQL 9.6 support is available

Commercial vendors offer security patches beyond EOL. Compare your options.

Compare Options →
All Amazon RDS for PostgreSQL Versions
VersionLatestEOL DateStatus
9.6 9.6.24 Apr 30, 2022 EOL
10 10.23 Apr 30, 2023 EOL
11 11.22 Feb 29, 2024 EOL
12 12.22 Feb 28, 2025 EOL
13 13.23 Feb 28, 2026 EOL
14 14.23 Feb 28, 2027 Active
15 15.18 Feb 29, 2028 Active
16 16.14 Feb 28, 2029 Active

What does Amazon RDS for PostgreSQL 9.6 end of life mean?

When Amazon RDS for PostgreSQL 9.6 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Amazon RDS for PostgreSQL 9.6 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Amazon RDS for PostgreSQL 18 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Amazon RDS for PostgreSQL 9.6 reach end of life?
Amazon RDS for PostgreSQL 9.6 reached end of life on April 30, 2022. This version is no longer receiving security patches.
Is Amazon RDS for PostgreSQL 9.6 still supported?
No. Amazon RDS for PostgreSQL 9.6 reached end of life on April 30, 2022 and is no longer receiving security patches.
What should I upgrade to from Amazon RDS for PostgreSQL 9.6?
The recommended upgrade from Amazon RDS for PostgreSQL 9.6 is Amazon RDS for PostgreSQL 18 — the latest actively supported version. Check the Amazon RDS for PostgreSQL full timeline for all supported versions.
What are the security risks of running Amazon RDS for PostgreSQL 9.6 past EOL?
When Amazon RDS for PostgreSQL 9.6 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Amazon RDS for PostgreSQL should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →