Skip to main content
NewDependency Trust 2026 Report68% of observed components were more than two years old.Get the report
CleanStart

Advisory: CVE-2026-119618, remote code execution in Apache mod_http2

CVE-2026-119618CVSS 9.8CriticalFixedPublished

A race condition in Apache HTTP Server's HTTP/2 module lets an unauthenticated attacker corrupt the heap of a server worker by sending crafted HTTP/2 traffic, with remote code execution as the documented outcome.

CleanStart httpd is fixed in 2.4.71-r0 and 2.4.71-r0-dev, published 19 November 2026. If you run any earlier CleanStart httpd tag with HTTP/2 enabled, move to 2.4.71-r0 now.

What happened

On 11 November 2026 the Apache Software Foundation published its advisory and released Apache HTTP Server 2.4.71, which contains the fix. The flaw was reported twice independently: by Anthropic's OSS Scanner on 26 October 2026, and by Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research on 3 November 2026. The fix merged upstream on 9 November 2026 (Apache Software Foundation advisory, 11 November 2026; F5 Labs, 17 November 2026).

The defect sits in assign_headers() in mod_http2. Two threads on the same HTTP/2 connection reach shared stream state without synchronisation while the module writes a synthesised Content-Length: 0 into the connection's stream table. The result is heap corruption inside the httpd child process, and from there remote code execution.

Two properties matter for triage:

  • No credentials are required. Reachability over HTTP/2 is the whole precondition. A server that negotiates h2 or h2c is in scope.
  • The Apache advisory publishes no workaround. Disabling HTTP/2 removes the attack surface. Upgrading is the fix.

Impacted packages and versions

Component

Affected

Fixed

Apache HTTP Server (httpd), mod_http2

2.4.55 through 2.4.70

2.4.71

Am I affected?

Yes, if your image is one of these tags: 2.4.70-r0, 2.4.70-r0-dev, 2.4.68-r1, 2.4.68-r1-dev, 2.4.68, 2.4.68-dev, 2.4.66, 2.4.66-dev.

No, if your image is 2.4.71-r0 or 2.4.71-r0-dev.

Yes, separately, if you build your own image against mod_h2 2.0.8 through 2.0.42 from GitHub. That module has no fix.

Not sure which one you run? This prints the version and whether the HTTP/2 module is loaded:

docker run --rm <your-image> sh -c 'httpd -v; httpd -M 2>/dev/null | grep http2'

If the second line prints nothing, mod_http2 is absent and this flaw cannot reach you. If it prints http2_module, you are exposed as soon as HTTP/2 is switched on, which happens when the Protocols directive includes h2 or h2c.

Resolution

Status as of 19 November 2026, from the tag listing on images.cleanstart.com/images/httpd/tags. Ten tags are published.

Tag

VEX status

2.4.71-r0, 2.4.71-r0-dev

fixed

CVE IDs, CWE and references

Identifier

Also known as

Description

CVE-2026-119618

EUVD-2026-123532, GHSA-hjhf-gpg9-qqfj

CWE-362, concurrent execution using shared resource with improper synchronisation in mod_http2 assign_headers(), leading to RCE