The Apache HTTP Server project shipped httpd 2.4.71 on Nov. 11, 2026. The release fixes three vulnerabilities, and one of them should move to the top of every web team's patch list. CVE-2026-119618 is a critical bug in mod_http2, the module that gives Apache HTTP/2 support. According to the project's security advisory, it involves heap corruption and can lead to remote code execution. Red Hat says the attacker does not need to log in.
The affected range is wide. Every httpd release from 2.4.55 through 2.4.70 is vulnerable, and so is the standalone mod_h2 module published on GitHub, versions 2.0.8 through 2.0.42. If you run Apache with HTTP/2 turned on and haven't patched yet, assume you're exposed.
What actually went wrong
The flaw is in a function called assign_headers(). Apache's advisory calls it "Concurrent Execution using Shared Resource with Improper Synchronization," the textbook description of a race condition. In plain terms, two threads touch the same memory at the same time without coordinating, and the result is corrupted data.
Red Hat Product Security gives the clearest account of the mechanics. HTTP/2 lets one connection carry many requests at once, and the module handles those concurrent requests using multiple threads. In vulnerable builds, a worker thread writes into memory owned by the connection thread through a shared, lock-free allocator: a fast memory manager that skips the locking needed to keep threads from colliding. When the timing goes wrong, the server's internal memory is corrupted. Heap corruption is a well-known route to arbitrary code execution in C programs like httpd.
Red Hat's description also explains why its own products got a lower rating. More on that below.
How bad is it?
Apache rates the bug critical. Red Hat's CVE page assigns a CVSS v3 base score of 9.8 (network attack vector, low complexity, no privileges required), which is near the top of the scale and typical of unauthenticated network RCE. The same page showed no NVD or cve.org score at the time we read it, and Red Hat notes that its scores can differ from NVD's. If your scanner pulls severity only from NVD, it may under-rate this finding for now.
Sources disagree on how close attackers are to a working exploit. The Hacker News reports that security company Wiz said no exploit was available and no exploitation in the wild had been reported. Red Hat's CVE page goes further. It says public research has demonstrated a reliable exploit against a default-configured server with mod_http2 enabled, but it does not name that research. ZeroDayFeed has not independently confirmed either claim. The safe reading: no confirmed attacks yet, but at least one major vendor says reliable exploitation has been demonstrated. Plan accordingly.
Who found it
Apache credits Anthropic's OSS Scanner, which reported the flaw on Oct. 26, and Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research, who reported it on Nov. 3. The fix landed in commit 824beab, dated Nov. 11, the same day 2.4.71 shipped. The project went from first report to public release in a little over two weeks.
Why the RHEL rating is lower
Red Hat rates the CVE Critical overall but Important on Red Hat Enterprise Linux 9 and 10. Its reasoning: the mod_http2 packages in those releases allocate each HTTP/2 stream from a separate allocator, which substantially increases the complexity of exploiting the flaw. RHEL 8 and earlier are not affected. Red Hat has also published a security bulletin, RHSB-2026-017.
The Hacker News lists the fixed RHEL packages:
- RHEL 9: mod_http2-2.0.26-7.el9_9.1 (RHSA-2026:98981)
- RHEL 10: mod_http2-2.0.29-5.el10_3.1 (RHSA-2026:98978)
Important still means patch. It is not a reason to wait.
Debian users have fewer options for now. Per The Hacker News, Debian's unstable branch (sid) has the fix in apache2 2.4.71-1, but bookworm, trixie and forky were still listed as vulnerable when it reported. Watch your distribution's security tracker and apply the backport as soon as it appears.
The mod_h2 problem
Some administrators run the standalone mod_h2 module from GitHub instead of the copy bundled with httpd. Those users have a bigger problem. According to The Hacker News, the mod_h2 repository has been read-only since it was archived on June 9, and its release list ends at 2.0.42, the last affected version. Versions 2.0.8 through 2.0.42 are affected, and no fixed mod_h2 release has been published. If you rely on standalone mod_h2, the realistic path is to move to the mod_http2 bundled with httpd 2.4.71, or your distribution's patched package, and stop using the archived module.
Didn't we just patch HTTP/2?
Many of you did. Apache fixed an earlier HTTP/2 flaw, CVE-2026-23918, in httpd 2.4.67 on May 4. The Hacker News points out that servers updated to that release, or to any later one up to 2.4.70, still run a version the new flaw affects. So a server patched for the spring issue is not protected now. Check the version you're actually running, not the date of your last HTTP/2 fix.
The rest of the release
Version 2.4.71 also fixes two lower-priority bugs. CVE-2026-106023, rated important, is a NULL pointer dereference in mod_md, Apache's module for automatically getting and renewing TLS certificates through ACME services like Let's Encrypt. Apache's advisory says it leads to a child process crash, so the main risk is denial of service. The third fix is a low-severity one-byte stack buffer overwrite in mod_vhost_alias, which maps hostnames to directories for mass virtual hosting. Neither is as urgent as the mod_http2 flaw, but upgrading to 2.4.71 covers all three.
What It Means for Defenders
Who is affected: Any Apache HTTP Server from 2.4.55 through 2.4.70 with mod_http2 loaded and HTTP/2 enabled, plus any server running standalone mod_h2 2.0.8 through 2.0.42. Red Hat says servers that serve only HTTP/1.1 are not affected. On RHEL, versions 9 and 10 are affected at Important severity, and RHEL 8 and earlier are not affected.
What to do, in priority order:
- Inventory. Find every Apache instance you run: internet-facing web servers, reverse proxies, appliances and container images built on httpd. Record the version and whether mod_http2 is loaded. Don't forget vendor products that bundle Apache, which may need their own update.
- Upgrade. Move to httpd 2.4.71, or install your distribution's patched package. On RHEL 9 and 10 that means the mod_http2 packages in RHSA-2026:98981 and RHSA-2026:98978. Debian stable users should watch for backports to bookworm, trixie and forky.
- Retire standalone mod_h2. It is archived and has no fix. Switch to the patched bundled module.
- If you can't patch yet, turn off HTTP/2. Wiz's suggested workaround, reported by The Hacker News, is to remove h2 and h2c from Apache's Protocols directive so it reads
Protocols http/1.1. Protocols can be set per virtual host, so check every vhost and included config file, not just the main server config. A single forgotten vhost leaves the server exposed. Treat this as a stopgap, not a permanent setting. - Don't wait for NVD. Red Hat's page showed no NVD score for this CVE when we read it. Use Apache's critical rating and Red Hat's 9.8 for prioritization, and override any scanner that shows it as unscored or low.
- Watch for compromise. No exploitation has been publicly reported, but Red Hat's statement that a reliable exploit has been demonstrated is reason enough to look closely at internet-facing HTTP/2 servers. Watch for unexpected worker crashes, segmentation faults in the error log, and unfamiliar child processes started by the httpd user.
Federal contractors working toward CMMC may want to log this under their flaw remediation process. A critical, unauthenticated RCE in a common internet-facing service is the kind of finding that fits a short, documented patch timeline.
For most teams this is a routine but urgent fix: a vendor patch is available and a clean workaround exists. The trouble spots are the unmanaged ones, such as the old reverse proxy, the appliance nobody owns, or the container image built last spring. Find those first.