1-minute read
What a defender needs to know
Apache HTTP Server 2.4.55 through 2.4.70 contains CVE-2026-119618, a race in HTTP/2 mod_http2 function assign_headers() that can corrupt heap memory and lead to remote code execution. Apache released the fix in 2.4.71 on November 11. Wiz Research describes a remote, unauthenticated attack path; it reported no observed exploitation when it published that day.
Start with public Apache front ends. Match each running binary or container image to its package version, and check the effective Protocols setting and a client connection’s negotiated protocol. A loaded mod_http2 module alone is less specific than a connection negotiating h2 or h2c on an affected build. Apache also lists standalone GitHub mod_h2 versions 2.0.8 through 2.0.42 as affected.
Upgrade to Apache HTTP Server 2.4.71 or a vendor build carrying the fix, then restart or replace the running process. If you need a temporary measure, Wiz recommends removing h2 and h2c from the effective Apache configuration and restricting the listener to HTTP/1.1. Verify the running build and negotiate a new client connection: it should use the fixed build, or HTTP/1.1 while the temporary restriction is in place. Investigate unexpected Apache child-process crashes or restarts in context; these events alone are not a fingerprint for this CVE.