Apache HTTP Server 2.4.67 Security Advisory — Immediate Action Required
Table of Contents
- Overview
- Critical Issue: CVE-2026-23918 (CVSS 8.8)
- Privilege Escalation: CVE-2026-24072
- Additional Fixes in 2.4.67
- Immediate Mitigation Steps
- FAQs
Overview
The Apache Software Foundation has disclosed multiple security vulnerabilities affecting the Apache HTTP Server, including a high-impact remote code execution issue.
Any system running 2.4.66 or earlier is exposed.
All issues are fixed in 2.4.67.
Summary:
- 5 vulnerabilities patched
- 1 critical RCE (CVE-2026-23918)
- Upgrade is the only full fix
Critical Issue: CVE-2026-23918 (CVSS 8.8)
Root Cause
A double-free memory corruption bug in the HTTP/2 implementation.
Attack Flow
- Server allocates memory for a request
- Attacker sends a crafted HTTP/2 early reset frame
- Memory is freed twice
- Heap corruption occurs
Impact
- Crash (DoS)
- Remote Code Execution (worst case)
Scope
- Affects only 2.4.66
Privilege Escalation: CVE-2026-24072
A flaw in mod_rewrite allows local privilege abuse.
Behavior
- Read arbitrary files
- Executes under Apache process context
Risk
- Cross-account data exposure in shared hosting
- Access to sensitive configs and credentials
Additional Fixes in 2.4.67
CVE-2026-28780 — mod_proxy_ajp
- Heap buffer overflow
- Malicious AJP backend
- Low severity
CVE-2026-29168 — mod_md
- Resource exhaustion via OCSP
CVE-2026-29169 — mod_dav_lock
- NULL pointer dereference
- Unauthenticated crash
- Legacy Subversion relevance
Immediate Mitigation Steps
1. Upgrade to 2.4.67
httpd -v
# or
apache2 -v2. If upgrade is delayed: disable HTTP/2
# Comment out or remove
LoadModule http2_module modules/mod_http2.so
# or if using cPanel/WHM
yum/dnf remove ea-apache24-mod_http23. Remove unused modules
# Example (cPanel EA4)
yum remove ea-apache24-mod_dav_lock4. Restrict .htaccess write access
- Audit user permissions
- Prefer centralized configs
AllowOverride None5. Review loaded modules
apachectl -MFAQs
Is disabling HTTP/2 enough?
No. It removes the RCE vector only. Other issues remain.
How do I check my version?
httpd -v
# or
apache2 -vIs this being actively exploited?
No confirmed exploitation as of May 5, 2026. Expect PoCs soon.
Where to get the patch?
From official Apache distribution channels.