No. Apache 2.4 is supported and no end-of-life date has been announced yet.
- Released
- 21 February 2012
- Security support ends
- No date announced
- Latest release
- 2.4.71 · 11 November 2026
- Long-term support
- No
What this means for your servers
Apache 2.4 is safe to run. Install updates regularly so you stay on the latest release in this cycle (2.4.71).
How to check if you’re running Apache HTTP Server 2.4
CLI
apache2 -v # Debian/Ubuntu
httpd -v # RHEL-familyWhat to upgrade to
Apache 2.4 is already the newest recommended release.
Apache 2.4 is the only supported branch and gets patch releases within it, so staying current means installing your distribution’s updates. Distributions backport fixes, so check the package changelog rather than the version number alone.
Find end-of-life software before an auditor does
The Statance agent reports the Apache HTTP Server version on every server it runs on and raises a security finding when it goes past end of life or falls behind the latest patch, along with known CVEs from OSV.dev and CISA’s Known Exploited Vulnerabilities list. Security monitoring is included in Pro and Business. How security monitoring works.
Other Apache HTTP Server releases
| Release | Status | Security support ends |
|---|---|---|
| Apache 2.2 | End of life | 11 July 2017 |
| Apache 2.0 | End of life | 10 July 2013 |
| Apache 1.3 | End of life | 3 February 2010 |
All Apache HTTP Server end-of-life dates →
FAQ
Is Apache 2.4 end of life?
No. Apache 2.4 is supported and no end-of-life date has been announced yet.
Can I keep running Apache 2.4 after end of life?
It keeps working, but new vulnerabilities will not be fixed, so every newly published CVE stays open on your server. Scanners and compliance frameworks (PCI DSS, SOC 2, Cyber Essentials) treat unsupported software as a finding.
What is the latest version of Apache 2.4?
The latest release in this cycle is 2.4.71, released on 11 November 2026.
Lifecycle data from endoflife.date/apache-http-server, refreshed 17 November 2026. Vendors occasionally change dates; check the vendor’s own lifecycle page before making a compliance decision.
Stop tracking end-of-life dates by hand.
Statance flags end-of-life and vulnerable software on every server automatically.