Quick answers
- Is CVE-2026-119618 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119618 being exploited in the wild.
- How severe is CVE-2026-119618?
- Informational severity, published 11 November 2026.
- Which products and versions are affected?
- Apache HTTP Server 2.4.55 through 2.4.70; Apache Mod H2 2.0.8 through 2.0.42.
- Is there a fix for CVE-2026-119618?
- Yes: fixed in Apache HTTP Server 2.4.71. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-119618 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-119618?
- Check whether you run Apache HTTP Server or Apache Mod H2 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Apache HTTP Server 2.4.71
Technical details
A concurrent execution vulnerability with improper synchronization exists in the assign_headers() function of mod_http2, where shared resources are accessed without adequate locking, leading to heap corruption. The vulnerability is reachable over the network via HTTP/2 connections and requires no authentication or user interaction. An attacker can exploit this to achieve remote code execution on the affected server.
Affected products
- Apache HTTP Server 2.4.55 through 2.4.70
- Apache mod_h2 2.0.8 through 2.0.42
Timeline
- 2026-11-11: disclosed: CVE-2026-119618 published
- 2026-11-11: patched: Apache HTTP Server 2.4.71 released with fix