IT Guy vs Ninja Hacker: Patch Apache HTTP/2 RCE Now

In our new scenario video, a ninja hacker floods an Apache server with two HTTP/2 streams that collide over the same header table. A race in assign_headers() inside mod_http2 corrupts heap memory and, in the story, hands him a root shell without a password. The IT guy notices an odd flicker in rack seven, watches…

The YouTube player loads only when you press play. Open on YouTube

In our new scenario video, a ninja hacker floods an Apache server with two HTTP/2 streams that collide over the same header table. A race in assign_headers() inside mod_http2 corrupts heap memory and, in the story, hands him a root shell without a password. The IT guy notices an odd flicker in rack seven, watches the Take Away Supports lesson on his PC, applies the verified fix, and wins the fight with four moves that map to the four real recovery steps.

Watch the video: https://youtu.be/cEI49nBzKcA

The cartoon is fictional. The two stickman characters were drawn from scratch, and the character voices are AI-generated. The closing voice was supplied by the channel. The vulnerability and the remediation steps below are real and checked against the sources at the end.

What is CVE-2026-119618?

CVE-2026-119618 is a heap-corruption issue in Apache’s HTTP/2 module. When concurrent HTTP/2 streams race while assigning headers, memory can be corrupted, which can lead to unauthenticated remote code execution on a vulnerable server.

Affected configurations

  • Apache httpd 2.4.55 through 2.4.70 when mod_http2 is enabled with h2 or h2c.
  • Standalone mod_h2 2.0.8 through 2.0.42.

At research time, no confirmed in-the-wild exploitation was found. That does not make this safe to ignore: unauthenticated RCE on a public web server is a patch-now class of bug.

The permanent fix

Upgrade to:

  • Apache httpd 2.4.71, or
  • your distribution’s fixed mod_http2 package.

Vendor package examples:

  • RHEL 9: mod_http2-2.0.26-7.el9_9.1
  • RHEL 10: mod_http2-2.0.29-5.el10_3.1

Restart or reload Apache after the update, then verify the old module is no longer loaded.

Temporary mitigation if you cannot patch immediately

Restrict the server to HTTP/1.1 until the fixed build is installed:

Protocols http/1.1

Then restart or reload httpd and confirm the virtual host no longer negotiates h2 or h2c. This is a bridge, not a replacement for the patch.

The four fight moves in the video

  1. Twin streams → HTTP/1.1 only: remove h2 and h2c while you prepare the patch.
  2. No password → patch 2.4.71: close the unauthenticated RCE path with the fixed Apache release.
  3. Heap crack → vendor build: install the fixed distribution package, not just a config tweak.
  4. Root shell → restart and verify: reload httpd and confirm the old module is gone.

Quick checklist

  • [ ] Inventory httpd 2.4.55–2.4.70 and standalone mod_h2 2.0.8–2.0.42 hosts.
  • [ ] Check which virtual hosts advertise h2 or h2c.
  • [ ] Patch to Apache 2.4.71 or the fixed vendor package.
  • [ ] If patching is delayed, set Protocols http/1.1, restart, and verify.
  • [ ] Confirm no vulnerable module remains loaded after the restart.

Sources

  • https://httpd.apache.org/security/vulnerabilities_24.html
  • https://www.cve.org/CVERecord?id=CVE-2026-119618
  • https://access.redhat.com/security/cve/CVE-2026-119618
  • https://thehackernews.com/2026/11/critical-apache-http2-flaw-could-let.html

Leave a Reply

Your email address will not be published. Required fields are marked *