CVE-2026-119618: Apache HTTP Server mod_http2 RCE

4 min read

The Apache HTTP Server project has published CVE-2026-119618. It is a race condition (CWE-362, concurrent execution using a shared resource with improper synchronization) in assign_headers() in mod_http2, the module that implements HTTP/2. Apache's advisory is titled “heap corruption and RCE in assign_headers” and says the flaw can lead to remote code execution. Apache rates it Critical. The CVSS 3.1 score from CISA-ADP, as shown on NVD, is 8.1 (High), with the vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. That means it is reachable over the network with no privileges and no user interaction, but attack complexity is rated high.

Apache released httpd 2.4.71 with the fix on 2026-11-11 and announced the issue on oss-security the same day. NVD published the record on 2026-11-11. According to the Apache advisory, the bug was reported on 2026-10-26 by Anthropic's OSS Scanner (tracked as ANT-2026-MAPKT6MZ) and independently on 2026-11-03 by Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research. Debian released DSA-6620-1 for apache2 on 2026-11-12. It fixes this CVE and two other apache2 CVEs.

Exploitation status

As of this writing, exploitation in the wild is not known. CISA has no Known Exploited Vulnerabilities (KEV) entry for this CVE, and none of the advisories reviewed for this alert report attacks.

Who is affected

The vulnerable code is in mod_http2. Upstream lists these affected and fixed releases:

ProductAffectedFixed
Apache HTTP Server2.4.55 to 2.4.702.4.71
mod_h2 (standalone, GitHub)2.0.8 to 2.0.42not stated in the advisory
Debian 13 (trixie) apache2versions before 2.4.71-1~deb13u12.4.71-1~deb13u1 (DSA-6620-1)

The Debian security tracker lists the issue as resolved for trixie in 2.4.71-1~deb13u1. Debian has not yet assigned an urgency. For other Debian releases, see the tracker page. On Debian, mod_http2 ships in the apache2-bin package, so any host with Debian's apache2 installed has the vulnerable code on disk. The advisory does not say whether a server that has HTTP/2 disabled can be exploited (see below).

What admins should do now

Install the fixed packages on Debian 13 and check the installed version:

apt update
apt install --only-upgrade apache2 apache2-bin apache2-data apache2-utils
dpkg-query -W apache2-bin

The output should show 2.4.71-1~deb13u1. A running httpd keeps the old code in memory until it restarts, so restart it and confirm that it comes back up:

systemctl restart apache2
systemctl status apache2 --no-pager

Then check whether HTTP/2 is active at all:

apache2ctl -M | grep http2
grep -ri "^\s*Protocols" /etc/apache2/

The Apache advisory, the oss-security post and DSA-6620-1 do not list a workaround. Updating is the fix. If a host cannot be patched right away, one interim option is to stop negotiating HTTP/2, since the flaw is in the HTTP/2 module. This is not vendor guidance, and it is not confirmed to fully mitigate the issue:

Protocols http/1.1
a2enconf zz-no-h2
apache2ctl configtest
systemctl reload apache2

Also check for Protocols lines inside individual vhosts. They override the global setting. If the module is not needed at all, a2dismod http2 removes it, provided no config still relies on HTTP/2-only directives. Remove this workaround after updating if clients need HTTP/2. If you build mod_h2 from GitHub or vendor it inside an appliance or container image, upgrade it separately. Distribution packages do not cover those copies. A wider checklist for exposed web servers is in Web Server Security Baseline on Debian 13.

What we don't know yet

  • Apache's advisory is short. It does not say which request patterns or configurations are needed to reach the vulnerable code path.
  • The advisory does not say whether a server with mod_http2 loaded but HTTP/2 not negotiated (no h2 or h2c in Protocols) can be exploited.
  • The advisory does not name a fixed release for the standalone mod_h2 module from GitHub.
  • Debian has not yet assigned an urgency to the issue in its tracker.
  • The difference between Apache's Critical rating and the CVSS 8.1 (High, high attack complexity) score has not been explained. It is unclear how reliable exploitation of the race is in practice.
  • No exploitation has been reported so far. That may change once more details become public.

Sources