Skip to main content
Report · SecurityWeekAbout CVE-2026-119618Published

Apache Patches Critical HTTP Server RCE Found by Anthropic, Google

Source SecurityWeek

0
Compare
Authoritative record:CVE-2026-119618· High

Not known to be exploited · fixed in 2.4.71 : patch Apache HTTP Server soon.

Data as of 12 Nov 2026, 15:48 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 2.4.71

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Apache Software FoundationApache HTTP ServerAffected
  • >=2.4.55 <=2.4.70
Fixed in–
Apacheapache/httpdpkg:rpm/apache/httpdOther threatsAffected
  • >=2.4.55 <=2.4.70
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fixed version, Apache HTTP Server 2.4.71, has been released and should be installed to remediate this vulnerability. If immediate patching is not feasible, disabling HTTP/2 on the server provides a temporary mitigation. Note that application-level updates, such as WordPress security patches, do not address this underlying server vulnerability.

Description

CVE-2026-119618 is a critical remote code execution vulnerability in the Apache HTTP Server's mod_http2 module, affecting versions 2.4.55 through 2.4.70. It arises from a race condition that allows unauthenticated attackers to execute arbitrary code on servers with HTTP/2 enabled. The flaw was patched in version 2.4.71. Disabling HTTP/2 can serve as a temporary mitigation if patching is not immediately possible.

References

Community reviews

Loading reviews…