Contact us
← Article questionsDoes this affect us?

CVEHit Business Advisory by IntegrityLab.ai

Does this affect us?

Apache web server HTTP/2 flaw reportedly exploited — CVE-2026-119618: Business Triage

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.

← Back to article questions

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…