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.
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.