UPDATE: If records show a break-in, start incident response now. Update affected Apache web servers to Apache 2.4.71 now, whether or not HTTP/2 appears to be on, because sources conflict on whether attacks are under way.
The reported finding
mod_http2 flaw may allow remote code execution
Original advisory →- Required conditions
-
- The affected Apache module is mod_http2.
- Its module identifier is http2_module.
- Apache HTTP Server 2.4.55 through 2.4.70 is the affected server line.
- GitHub mod_h2 2.0.8 through 2.0.42 is the separate affected line.
- HTTP/2 is enabled for that component through the Protocols setting.
- h2, HTTP/2 with encryption, can reach that component.
- h2c, HTTP/2 without encryption, can also reach that component.
- A request can reach that handling.
- These sources do not list a narrower trigger configuration.
- Reported outcome
-
- Apache's advisory title is "mod_http2: heap corruption and RCE in assign_headers". Apache says an attacker could run their own code on the server.
- The CVE record names the weakness CWE-362.
- Apache describes the severity as critical.
- CISA ADP reports CVSS 3.1 8.1 High in the CVE record. Apache separately rates the flaw critical. Singapore CSA calls it high-severity.
- CISA vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.
- AV:N means network-reachable, including internal networks. It is not proof of Internet exposure.
- High attack complexity means success depends on conditions outside the attacker’s control. It does not remove the affected HTTP/2 conditions.
- Possible code execution is not assured compromise of every matching server.
- What an attacker could reach is limited by the server's permissions and the data it can read.
- Reported exploitation (added November 18, 2026)
-
- Singapore CSA alert AL-2026-164, dated November 17, 2026, is titled "Active Exploitation of Vulnerability in Apache HTTP Server's mod_http2".
- Its Known Exploitation section says: "This vulnerability is reportedly being actively exploited, and a proof-of-concept exploit is publicly available."
- CISA's SSVC assessment in the CVE record, dated November 13, 2026, says Exploitation: none.
- CVE-2026-119618 is not in the CISA KEV catalog, version 2026.11.17.
- These sources disagree. This page does not resolve the disagreement.
- The sources do not say when or where exploitation was observed, by whom, or how widely. They give no install or exposure counts and no attack rates.
- The sources do not say where the proof of concept is published. This page links to none.
Fix guidance
- Apache's advisory names Apache HTTP Server 2.4.71, released November 11, 2026, as the fix.
- Version boundaries:
- Singapore CSA lists Apache HTTP Server 2.4.55 to before 2.4.71 with mod_http2 enabled as affected, and recommends updating immediately.
- The CVE record lists Apache HTTP Server 2.4.55 through 2.4.70 as affected but does not name a fixed version.
- Every 2.4.71 instruction applies to Apache HTTP Server only.
- GitHub mod_h2 2.0.8 through 2.0.42 is affected. These sources give no fixed mod_h2 release.
- These sources confirm no Linux distribution or hosting package fix.
- Exploitation records and dates:
- Singapore CSA alert AL-2026-164, November 17, 2026: reportedly actively exploited, with a publicly available proof of concept.
- CISA assessment in the CVE record, dated November 13, 2026:
- Exploitation: none.
- Automatable: no.
- Technical Impact: total.
- The CVE record was published November 11, 2026 and last updated November 15, 2026. We found no later CISA assessment on November 18, 2026.
- The CISA assessment predates the Singapore CSA alert by four days. These sources do not show whether CISA has reviewed the report.
- Exploitation: none means CISA had no evidence of exploitation in that assessment. It does not prove no attacks occurred or that your systems are safe.
- Automatable: no means CISA does not assess the exploitation path as reliably automatable. It does not measure attack frequency.
- KEV catalog 2026.11.17, released November 17, 2026 at 17:53 UTC, has no entry for CVE-2026-119618.
- No KEV entry is not proof of no exploitation.
- Primary sources were retrieved November 18, 2026.
What IntegrityLab.ai can check
- This advisory does not mean IntegrityLab.ai detects CVE-2026-119618.
- When enabled for an authorized assessment, IntegrityLab.ai's discovery records reachable web services and the server name they return. This gives your administrator a starting point.
- It does not currently offer:
- A validated check for CVE-2026-119618.
- An HTTP/2 test.
- A check of which Apache modules are loaded.
- Confirmation of a package's fixes.
- Proof of compromise.
- Confirmation of reported exploitation.
- What an observation can establish:
- A displayed Apache name or version is a clue, not proof of the installed build or fix status.
- A missing name does not rule Apache out.
- If another server handles the public connection, its response does not show the Apache configuration behind it.