Apache HTTP Server 2.2 · Version Status
Apache HTTP Server 2.2 End of Life Date
Apache HTTP Server 2.2 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
Apache HTTP Server 2.2 is past end of life. This version no longer receives security patches. 3385 days past EOL — migrate to a supported version immediately.
EOL Date
Jul 11, 2017
3385 days past EOL
Latest Release
2.2.34
Standard release
Release Date
Dec 1, 2005
Apache HTTP Server 2.2 series
Lifecycle detail
Apache HTTP Server 2.2 was released on December 1, 2005 and support ended on July 11, 2017 — a supported lifespan of 11 years and 8 months, in line with the 11 years and 8 months median for Apache HTTP Server releases. The last patch it will ever receive is 2.2.34, published July 11, 2017 — on the day support ended. It has been without security patches for 9 years and 3 months.
Attack Surface
20/30 High tier
CISA KEV Exposure
20/20 Named in CISA 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 →
Extended Support
Extended Apache HTTP Server 2.2 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
All Apache HTTP Server Versions
| Version | Latest | EOL Date | Status |
|---|
| 1.3 |
1.3.42 |
Feb 3, 2010 |
EOL |
| 2.0 |
2.0.65 |
Jul 10, 2013 |
EOL |
| → 2.2 |
2.2.34 |
Jul 11, 2017 |
EOL |
| 2.4 |
2.4.69 |
EOL |
Active |
What does Apache HTTP Server 2.2 end of life mean?
When Apache HTTP Server 2.2 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Apache HTTP Server 2.2 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Apache HTTP Server 2.4 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Apache HTTP Server 2.2 reach end of life?
Apache HTTP Server 2.2 reached end of life on July 11, 2017. This version is no longer receiving security patches.
Is Apache HTTP Server 2.2 still supported?
No. Apache HTTP Server 2.2 reached end of life on July 11, 2017 and is no longer receiving security patches.
What should I upgrade to from Apache HTTP Server 2.2?
The recommended upgrade from Apache HTTP Server 2.2 is
Apache HTTP Server 2.4 — the latest actively supported version. Check the
Apache HTTP Server full timeline for all supported versions.
What are the security risks of running Apache HTTP Server 2.2 past EOL?
When Apache HTTP Server 2.2 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Apache HTTP Server should migrate immediately or implement compensating controls.