Contact us
← CVEHit Business AdvisoryApache HTTP Server mod_http2 flaw CVE-2026-119618: Business Triage

CVEHit Business Advisory by IntegrityLab.ai

Published · Updated

Apache web server HTTP/2 flaw reportedly exploited — CVE-2026-119618: Business Triage8.1/10High · CVSS 3.1CISA ADPFix availableApache 2.4.71CISA assessmentCVE.org sourceNo KEVChecked Nov 18

Update affected Apache web servers to Apache 2.4.71. Research: primary sources retrieved November 18, 2026.

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.

Check these three things.

  1. System owner: confirm whether each Apache web server needs the Apache 2.4.71 fix.
    Affected versions and package fixes
    • Apache HTTP Server 2.4.55 through 2.4.70 is affected.
    • Apache HTTP Server 2.4.71 is the fixed release named by Apache.
    • mod_h2 from GitHub is a separate version series. Releases 2.0.8 through 2.0.42 are affected. These sources name no fixed mod_h2 release.
    • A hosting or Linux distribution package may carry its own fix under an older-looking version number. These sources do not confirm any such package fix.
    • An older-looking version number is not proof that the package lacks the fix.
    • For a server run by a hosting provider, ask the provider for the same records.
    • Record for each server:
      • Installed version or package.
      • Source of that version.
      • Date checked.
  2. Operations owner: check whether web requests, including internal ones, reach Apache with HTTP/2 turned on.
    When the risk applies
    • The risk applies when HTTP/2 is turned on in an affected Apache or mod_h2 and requests can reach it.
    • Singapore CSA says only servers with mod_http2 enabled are affected.
    • The CISA vector includes AV:N. That means network-reachable, including internal networks. It is not proof that a server is exposed to the Internet.
    • HTTPS is not required. HTTP/2 can also run without encryption.
    • Some sites have another server that receives visitors' requests first and passes them to Apache. This is called a reverse proxy. Its use of HTTP/2 does not show whether Apache uses HTTP/2.
    • A site offering HTTP/2 is not proof that Apache is behind it.
    • A server that had HTTP/2 reachable while it ran an affected version was exposed for that time, even if it is fixed now.
  3. Security owner: check whether internal records show unauthorized activity on the Apache servers.
    What the records can show
    • Records to review:
      • Web server logs.
      • System logs.
      • Security alerts for these servers.
      • Unexpected changes to website files.
      • Unexpected connections from these servers to other systems.
    • Limits:
      • These sources describe no specific signs of attacks on this flaw.
      • A report that others are being attacked is not evidence of harm on your servers.
      • Clean records do not prove that no attack happened.
      • Missing records leave the harm question open.

Do Now

  • System owner: do not treat 2.4.70 as already safe; update affected Apache web servers to Apache 2.4.71.
    Proof the update is done
    • Which servers run Apache HTTP Server 2.4.55 through 2.4.70.
    • Completion evidence for each server:
      • Installed version or package after the update.
      • Source of that record.
      • Date checked.
    • For a provider package that claims a fix below 2.4.71, the provider's notice naming CVE-2026-119618.
    • For GitHub mod_h2 2.0.8 through 2.0.42, confirmation of which fixed release applies. These sources do not name one.
  • Operations owner: list each server where HTTP/2 requests reach Apache.
    Records that show HTTP/2 use
    • Whether the HTTP/2 module, http2_module, is loaded.
    • Whether the Protocols setting turns on HTTP/2:
      • h2, HTTP/2 with encryption.
      • h2c, HTTP/2 without encryption.
    • Which server, if any, receives requests before Apache.
    • Whether internal systems can also send requests to it.
    • Source and date of each record.
  • Security owner: review affected servers' records for signs of unauthorized activity.
    Where to look first
    • Start with servers that ran an affected version with HTTP/2 reachable, including servers updated since.
    • If records show a break-in, escalate to the incident-response owner now.
    • Act on signs of a break-in even if this flaw cannot be shown as the cause.

Do Next

  • Security owner: recheck CISA and Apache for changes to this flaw's exploitation status.
    What to recheck
    • The CISA assessment in the CVE record, last dated November 13, 2026.
    • The CISA Known Exploited Vulnerabilities (KEV) catalog entry for CVE-2026-119618. It was absent from catalog 2026.11.17.
    • Apache's security page and Singapore CSA alert AL-2026-164.
    • Date of each recheck.

Check your own records.

  • Use your approved AI tool.
  • Require evidence. Flag unknowns.

Read the prompt

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.

How to read the score

CISA ADP CVSS 3.1: 8.1 (High). Apache: Critical. Use the conditions and update history alongside the score to set your priorities.

Sources and vendor guidance

Need an independent review of your public exposure?

See IntegrityLab.ai →

How can we help?

Initial enquiries only. Omit passwords, access tokens, security reports or other sensitive information. We’ll arrange secure sharing if needed.

Privacy & data handling ↗. Submitting this form does not authorise an assessment.

Checking enquiry availability…