Skip to content
← All stories

Vulnerabilities

Critical Apache HTTP/2 flaw lets attackers run code on servers

A flaw in Apache HTTP Server's HTTP/2 module lets unauthenticated attackers run code remotely. Only servers with HTTP/2 enabled are affected. A fix is available in version 2.4.71.

Ross Grant3 min read

The short version

A serious bug in Apache HTTP Server's HTTP/2 module lets attackers take control of servers if HTTP/2 is enabled. The problem affects versions 2.4.55 to 2.4.70. A fix is available in version 2.4.71. Server admins should update or disable HTTP/2 to stay safe.

By the numbers

  • 9.8CVSS severity rating for the flawThe Hacker News
  • 2.4.55–2.4.70Affected Apache HTTP Server versionsThe Hacker News
  • 2.4.71Version with the fixThe Hacker News
  • 0Authentication needed to exploit the flawThe Hacker News

What happened?

A critical flaw in Apache HTTP Server's HTTP/2 module (mod_http2) allows unauthenticated attackers to run code on affected servers. The bug, tracked as CVE-2026-119618, affects versions 2.4.55 through 2.4.70 and is fixed in version 2.4.71, released on 11 November 2026. Only servers with HTTP/2 enabled are vulnerable. Red Hat and Amazon Linux have released fixes. No exploitation in the wild has been reported, according to Wiz.

Who is affected

The flaw affects Apache HTTP Server installations running versions 2.4.55 through 2.4.70 with the HTTP/2 module (mod_http2) enabled. Only servers with HTTP/2 turned on are at risk. This includes those using the Protocols directive set to "h2" (for HTTP/2 over TLS) or "h2c" (for HTTP/2 over plain TCP). The issue impacts both the main Apache project releases and distributions such as Red Hat Enterprise Linux 9 and 10, Amazon Linux 2, Amazon Linux 2023, and Amazon Linux 2027 Preview. Standalone builds of mod_h2 from version 2.0.8 through 2.0.42 are also vulnerable. Red Hat Enterprise Linux 8 and earlier are not affected, as they do not include the vulnerable code.

How the flaw works

Tracked as CVE-2026-119618, the vulnerability allows a remote, unauthenticated attacker to execute code on the server. This means an attacker who can reach the server does not need a username or password to exploit the flaw. If successful, they could take control of the server process. The flaw is rated 9.8 out of 10 on the CVSS scale, which measures severity. According to Red Hat, public research has shown a reliable exploit against a default server with mod_http2 enabled, though the specific research is not named. Security company Wiz said no exploit was publicly available and there were no reports of attacks in the wild as of the report date.

Is there a fix?

A patch is available in Apache HTTP Server version 2.4.71, released on 11 November 2026. Red Hat shipped fixes for its affected products the same day, but rated the flaw as Important rather than Critical for Red Hat Enterprise Linux 9 and 10, due to extra security measures in their builds. Admins should update to the fixed version as soon as possible. If updating is not possible, removing "h2" and "h2c" from the Protocols directive (leaving only "http/1.1") will disable HTTP/2 and prevent exploitation. There is no workaround offered by the Apache project itself. The standalone mod_h2 project has not published a fixed release and its repository is archived, so users should also disable HTTP/2 if they cannot update.

Timeline

  • 26 October 2026: Flaw reported by Anthropic's OSS Scanner.
  • Early November 2026: Google Cloud Vulnerability Research confirms the issue.
  • 11 November 2026: Apache HTTP Server 2.4.71 released with a fix. Red Hat and Amazon Linux ship patched versions.
  • 12 November 2026: Public reporting by The Hacker News [The Hacker News (opens in a new tab)].

What you should do

Admins running Apache HTTP Server should check if HTTP/2 is enabled and update to version 2.4.71 or their vendor's patched package. If an update is not possible, disable HTTP/2 by editing the Protocols directive. Monitor vendor advisories for updates, especially if using standalone mod_h2 builds.

Claimed vs confirmed

  • Unconfirmed

    Public research has demonstrated a reliable exploit against default servers with mod_http2 enabled.

    Red Hat's assessment says this, but does not name or link the research.

  • Confirmed

    No exploit is publicly available and no exploitation in the wild has been reported.

    Security company Wiz reported this on the day of public disclosure.

Why it matters

Apache HTTP Server is widely used to host websites and applications. This flaw lets attackers take control of servers without logging in, putting data and services at risk. Only servers with HTTP/2 enabled are affected, but the impact can be severe if not patched.

Key points

  1. Critical remote code execution flaw in Apache HTTP/2 module (CVE-2026-119618)
  2. Affects versions 2.4.55–2.4.70 with HTTP/2 enabled
  3. Fixed in Apache HTTP Server 2.4.71 and vendor-patched builds
  4. No authentication needed to exploit the flaw
  5. Admins should patch or disable HTTP/2 immediately

Sources

  1. The Hacker News

    Reference

The day's cyber news in 5 minutes.

Cyberend Daily is one short email with the stories that matter, written so anyone can follow.

Includes our free beginner roadmap · No spam · Unsubscribe anytime