RC RANDOM CHAOS

Apache patched a 9.8 HTTP/2 flaw November 14

CVE-2026-119618 lets unauthenticated attackers run code on Apache HTTP Server with HTTP/2 enabled; fixed in 2.4.71. How to check exposure and patch.

· 3 min read
Apache patched a 9.8 HTTP/2 flaw November 14

A remote attacker who can reach an Apache HTTP Server with HTTP/2 turned on can run code on it without authenticating and take full control of the server process. The bug is in mod_http2, tracked as CVE-2026-119618, and it affects versions 2.4.55 through 2.4.70. The fix is 2.4.71, released November 14. Red Hat, which ships Apache as part of Red Hat Enterprise Linux, rates it 9.8 out of 10 on CVSS.

Red Hat’s assessment says public research has demonstrated a reliable exploit against a server in its default configuration with mod_http2 enabled, though it does not name or link that research. Wiz, publishing the same day, said no exploit was available and no exploitation in the wild had been reported. With one vendor describing a working exploit, patch on the assumption that one exists.

Whether you’re exposed

HTTP/2 only runs where the Protocols directive turns it on. h2 is HTTP/2 over TLS, h2c is HTTP/2 over plain TCP. The directive can be set server-wide or inside a single virtual host, so check the server-wide configuration and every vhost. If neither token appears anywhere, the server is not affected.

The fix path

If you run the Apache HTTP Server project’s own releases, move to 2.4.71. That release also fixes a crash in mod_md, rated important, and a one-byte stack overwrite in mod_vhost_alias, rated low.

Distributions ship their own builds with their own version numbers, so the project version is not what you check on a packaged system. On Red Hat Enterprise Linux 9 the fix ships as mod_http2-2.0.26-7.el9_9.1. Red Hat shipped fixes for RHEL 9 and 10 on November 14 and rates the flaw Important on those releases rather than Critical: its packages give each HTTP/2 stream its own memory allocator, which it says makes the attack much harder. RHEL 8 and earlier do not contain the vulnerable code. Debian’s status is in its security tracker and Amazon Linux’s in the Amazon tracker. Ubuntu’s CVE tracker had no page for the flaw as of November 15.

The standalone build of the module, published on GitHub as mod_h2, is affected from 2.0.8 through 2.0.42. No fixed release has been published so far. The 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.

If you can’t update yet

The Apache advisory offers no workaround. Wiz’s guidance for anyone who cannot update is to remove h2 and h2c from the Protocols directive and leave Protocols http/1.1. That drops HTTP/2 support but closes the exposure, and it applies to servers running the archived mod_h2 builds too.

Patching the previous HTTP/2 flaw does not cover this one. CVE-2026-23918 was fixed in 2.4.67 on May 4; a server on any version from 2.4.67 through 2.4.70 is still in the vulnerable range for CVE-2026-119618.

The flaw was reported to the project on October 26 by Anthropic’s OSS Scanner, a free scanning service for open-source projects that runs on the company’s AI models, and again last week by Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research.

Share

Keep Reading

Latest on the Wire

Full wire →

New signal daily · RSS

Stay in the loop

New writing delivered when it's ready. No schedule, no spam.