Apache Patches Critical HTTP/2 Flaw Allowing Remote Code Execution on Web Servers
What happened?
Apache has fixed a critical bug in its HTTP/2 module that could let a remote attacker run code on a web server. The flaw is tracked as CVE-2026-119618 and affects mod_http2. The fix came on November 11, 2026, in Apache HTTP Server 2.4.71. The bug sits in a function called assign_headers(). Apache says it is a concurrency problem, where shared resources are used without proper locking. Put simply, two parts of the code can touch the same piece of memory at the same time. That can damage the heap, the memory area a program uses while it runs, and this can lead to remote code execution.
Key details
- Apache fixed a critical HTTP/2 flaw in mod_http2 that allows remote code execution on web servers.
- The vulnerability is a concurrency issue in the assign_headers() function where shared memory lacks proper locking.
- Apache HTTP Server versions 2.4.55 through 2.4.70 are affected, plus standalone mod_h2 versions 2.0.8 through 2.0.42.
- Administrators are urged to upgrade immediately rather than wait for CVSS scores or detailed technical write-ups.
What is affected?
- Apache HTTP Server 2.4.55 through 2.4.70
- Standalone mod_h2 from GitHub versions 2.0.8 through 2.0.42
How do I fix or mitigate it?
- If immediate upgrade is not possible, limit the server to HTTP/1.1 until the update is applied.
What should defenders look for?
- Unusual crashes or worker-process restarts in server logs may indicate probing attempts.
Summarised by SecOraLens from Cyber Security News. Always read the original source before acting. How SecOraLens verifies advisories.
What to do next
Brief your board. Brief your team.
Executive risk briefs for governance, technical kill-chains for the SOC — delivered as advisories publish. Critical alerts within 1 hour. No spam, unsubscribe anytime.
