Ansible · Lifecycle Status

Ansible End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all Ansible versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

Ansible 13.6.0 is actively supported. No versions approaching EOL in the next 6 months.
Latest Active
13.6.0
13 series
Next EOL
None upcoming
Active Versions
1
of 13 total
EOL Versions
12
no longer patched
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 20202021202220232024202520262.92.10345678910111213TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
2.9 2.9.27 Oct 31, 2019 May 23, 2022 1447 days past EOL EOL
2.10 2.10.7 Sep 22, 2020 Feb 9, 2021 1915 days past EOL EOL
3 3.4.0 Feb 18, 2021 May 11, 2021 1824 days past EOL EOL
4 4.10.0 May 18, 2021 Dec 14, 2021 1607 days past EOL EOL
5 5.10.0 Dec 2, 2021 Jun 8, 2022 1431 days past EOL EOL
6 6.7.0 Jun 21, 2022 Dec 6, 2022 1250 days past EOL EOL
7 7.7.0 Nov 22, 2022 Jun 22, 2023 1052 days past EOL EOL
8 8.7.0 May 30, 2023 Dec 6, 2023 885 days past EOL EOL
9 9.13.0 Nov 21, 2023 Dec 3, 2024 522 days past EOL EOL
10 10.7.0 Jun 4, 2024 Dec 3, 2024 522 days past EOL EOL
11 11.13.0 Nov 19, 2024 Dec 9, 2025 151 days past EOL EOL
12 12.3.0 Sep 9, 2025 Dec 9, 2025 151 days past EOL EOL
13 13.6.0 Nov 19, 2025 Already EOL Supported Active

What does Ansible end of life mean for your organization?

When a Ansible version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.

Organizations running EOL Ansible should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Check your full stack for EOL risk

Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.

Open Stack Scanner →
Frequently Asked Questions
What is the end-of-life date for Ansible?
See the full table above for all Ansible version EOL dates.
What is the latest supported version of Ansible?
The latest active version of Ansible is 13.6.0. Always verify against the table above as support windows can change.
What happens when Ansible reaches end of life?
When Ansible reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Ansible?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Ansible versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →