Plan this weekVulnerabilities

Apache HTTP Server 2.4.71 fixes a critical mod_http2 flaw that can lead to remote code execution (CVE-2026-119618): update, or drop HTTP/2 until you can

Apache released 2.4.71 on 11 November 2026 to fix CVE-2026-119618, a heap corruption in mod_http2 that can lead to RCE in versions 2.4.55 through 2.4.70. Only servers with HTTP/2 enabled are affected, according to Red Hat. No exploitation was reported when it was published. How to check your server and what to do.

How urgent

Plan this week

Who is affected

Apache HTTP Server 2.4.55 through 2.4.70 with HTTP/2 enabled (mod_http2), and the standalone mod_h2 module 2.0.8 through 2.0.42; servers that serve only HTTP/1.1 are not affected, according to Red Hat

What to do

Check your version and whether HTTP/2 is on; update to Apache 2.4.71 or your distribution's fixed package; until then, serving only HTTP/1.1 (Protocols http/1.1) removes the exposure; put internet-facing servers first

Published 12 Nov 2026 · Sources last checked 12 Nov 2026No. 83 / 87

What happened

On 11 November 2026 the Apache HTTP Server project released version 2.4.71, which fixes three vulnerabilitiesVulnerability A weakness in software, a setting or a process that an attacker could use to get in or do harm. Tap again to open the glossary. One of them, CVE-2026-119618, is titled "mod_http2: heap corruption and RCERCE (remote code execution) A flaw that lets an attacker run their own code on your server or device from a distance. Tap again to open the glossary in assign_headers". The project describes it as a concurrent execution flaw using a shared resource with improper synchronization in assign_headers() that "can lead to RCE", and rates it critical. It affects Apache HTTP Server 2.4.55 through 2.4.70, and the standalone mod_h2 module from 2.0.8 through 2.0.42. The record credits Anthropic's OSS Scanner and Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research; the flaw was reported to Apache on 26 October (Anthropic) and 3 November (Google).

What the sources say about severity and exposure

  • Severity: Apache and the CVECVE A public ID number, like CVE-2026-12345, given to one specific security flaw so everyone can talk about the same bug. Tap again to open the glossary record say "critical" without a score. The NVD record was still "Received", with no CVSSCVSS score A number from 0 to 10 that rates how serious a flaw is in general. From 9.0 up it is called Critical. Tap again to open the glossary yet. Red Hat assigns its own CVSS v3.1 score of 9.8 (network, low complexity, no privileges, no user interaction) and rates RHEL 9 and 10 as Important because of how memory is allocated per stream.
  • Who is exposed: Red Hat says only servers with HTTP/2 enabled are affected, and servers configured to serve only HTTP/1.1 are not. Red Hat says RHEL 8 and earlier are not affected.
  • Exploitation: Wiz wrote, when it published, that no exploitExploit A piece of code or a technique that takes advantage of a specific flaw to get something the attacker should not get. Tap again to open the glossary was available and there were no reports of exploitation in the wild. We did not find the flaw in CISA's known exploited vulnerabilities catalog.
  • Fixed packages: Debian lists Apache 2.4.71-1 as fixed in sid and 2.4.71-1~deb13u1 in trixie, and still lists bookworm as vulnerable at the time we read it.
  • Temporary mitigation: Wiz suggests serving only HTTP/1.1 by setting Protocols http/1.1, which removes h2 and h2c.

How serious it is

A remote code execution flaw in a widely used web server is worth acting on this week if you serve HTTP/2. What lowers the urgency today is that nobody reported attacks when it was published and that disabling HTTP/2 closes the exposure. What raises it is that the fix is public, so attackers can study it. Treat internet-facing servers first.

What to do

  1. Find your version: run httpd -v or apache2 -v. If it is 2.4.55 to 2.4.70, you are in range.
  2. Check whether HTTP/2 is on: apachectl -M | grep http2 shows whether mod_http2 is loaded, and the Protocols directive in your configuration shows whether h2 or h2c is offered.
  3. Update to Apache 2.4.71 or to your distribution's fixed package, then restart Apache. If your distribution has not shipped a fix yet (Debian bookworm showed none when we read it), use the mitigation below.
  4. Until you can update, serve only HTTP/1.1: set Protocols http/1.1 and reload. This is Wiz's suggestion, not an Apache statement.
  5. Standalone mod_h2 users: move to a version newer than 2.0.42 once one exists; its repository is archived and we could not confirm a fixed release.
  6. Watch CISA's known exploited vulnerabilities list and your distribution's advisories for changes.

Steps 1 and 2 are ours.

What we could not confirm

The Apache page does not say whether authentication is needed; the "no privileges required" reading comes from Red Hat's score. The NVD record has no CVSS yet, and NVD and MITRE list the weakness as CWE-362 while Red Hat lists CWE-20. We could not confirm a fixed mod_h2 version: Wiz gives two different values and the repository has no newer release. We could not read Ubuntu's advisory, Red Hat's package table, or an Anthropic or Google write-up. We did not test the flaw ourselves.

Watch the short video

The video loads from YouTube (privacy-enhanced mode) only when you press play.

Comments

No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.

    We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.

    Sources and verification

    We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.

    Spotted a mistake? Email [email protected] and we will correct it and note the change.

    Get the free runbooks

    One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

    Send me the runbooks