Apache says concurrent execution in assign_headers() can corrupt heap memory and lead to remote code execution. The Apache security team rates the issue critical and fixed it in HTTP Server 2.4.71.The issue affects HTTP Server 2.4.55 through 2.4.70, according to Apache. For operational response steps, read the Apache HTTP Server patch and verification playbook. Teams tracking exposed installations can use their vulnerability intelligence platform to prioritize this CVE.
What it allows
How Can CVE-2026-119618 Lead to Remote Code Execution?
Apache identifies improper synchronization when mod_http2's assign_headers() uses a shared resource during concurrent execution. The resulting heap corruption can lead to remote code execution, according to its advisory. Apache does not describe a reliable attack sequence or state that every affected deployment is exploitable.
NVD's secondary CVSS 3.1 assessment assigns an 8.1 High score. Its vector describes a network attack with high attack complexity and no required privileges or user interaction. These vector properties are NVD's assessment, while Apache labels its own security impact critical.
What Is Known About Exploitation?
Brandefense's source pack counted nine public GitHub repositories whose names include CVE-2026-119618 as of November 13, 2026. The count includes research labs and scanners, so it does not establish nine working exploits or an intrusion. The repository descriptions have not been independently validated as proof of exploitability.
CISA's November 13, 2026 KEV catalog did not list the CVE. This dated catalog status does not determine whether exploitation occurred elsewhere. Treat exploitation status as unknown while checking systems for unexpected behavior.
Who is affected
Version Check
| Release Line | Affected Range | Fixed In |
|---|---|---|
| 2.4.x | 2.4.55 to before 2.4.71 | 2.4.71 |
For distribution packages and custom builds, check the supplier’s advisory.
Standalone mod_h2 boundary differs between Apache and NVD; verify it manually. Distribution packages may backport the fix.
Which Versions Are Affected by CVE-2026-119618?
Apache lists HTTP Server 2.4.55 through 2.4.70 as affected and 2.4.71 as the fixed release. The relevant module is mod_http2. Inventory internet facing and internal HTTP/2 deployments, including images and servers managed by another team.
Apache also lists standalone mod_h2 releases 2.0.8 through 2.0.42 as affected. NVD's configuration record instead ends its standalone range before 2.0.42. Because the sources disagree at that boundary, inspect the deployed mod_h2 build and obtain a vendor supported fix before clearing 2.0.42.
What Should Defenders Verify After Updating?
Update affected HTTP Server installations to 2.4.71 or a vendor package that explicitly carries the fix. Record the package release and validate the running server version after a restart. For distributor packages, confirm the vendor's backport status instead of judging safety by the upstream version string alone.
Check that mod_http2 is enabled where HTTP/2 service is expected. Review server error logs for crashes or abnormal child restarts around the exposure window, then investigate any suspicious events. Use the existing patch management process to retain the asset, package, and verification result.
Brandefense Blackhole counted 16 dark chat posts mentioning CVE-2026-119618 from August 16 through November 14, 2026. These are posts in one measured source and period, not verified incidents. The chat count and repository count represent separate sources that may overlap, so they should not be added.
Timeline
- 2026-10-26
Apache received the first report, credited to Anthropic's OSS Scanner.
- 2026-11-03
Apache received a separate report from Google Cloud Vulnerability Research.
- 2026-11-11
Apache fixed the issue in the 2.4.x branch and released HTTP Server 2.4.71.
What to do
-
Inventory affected HTTP/2 servers
List Apache HTTP Server 2.4.55 through 2.4.70 installations and determine where mod_http2 is loaded. Include standalone mod_h2 packages and record their exact vendor release.
-
Apply the Apache fix
Upgrade affected upstream HTTP Server installations to 2.4.71. For distribution packages, obtain the vendor's confirmed backport and document the patched package release.
-
Verify the running version
Restart the server, check the version and loaded modules, and compare the running build with the approved fixed package. Recheck every node behind a load balancer.
-
Review abnormal server behavior
Inspect error logs for crashes or unexpected child restarts during the exposure window. Investigate suspicious events with available host and network telemetry.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-119618 in Brandefense Atlas
The Atlas record of CVE-2026-119618: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Does CVE-2026-119618 affect every Apache HTTP Server version?
Apache lists versions 2.4.55 through 2.4.70 as affected. It released the fix in HTTP Server 2.4.71.
Does Apache HTTP Server 2.4.71 fix this issue?
Yes. Apache lists CVE-2026-119618 under the issues fixed in 2.4.71, released November 11, 2026.
Is standalone mod_h2 2.0.42 affected?
Apache includes 2.0.42 in its affected range, but NVD excludes it in its configuration data. Follow Apache's advisory and verify your vendor's patched build.
Is active exploitation confirmed?
The opened Apache and NVD records do not establish an incident. CISA's November 13 KEV catalog did not list this CVE, and research mentions do not prove exploitation.
Sources
- Apache HTTP Server 2.4 VulnerabilitiesApache Software Foundation
- CVE-2026-119618 RecordNIST NVD
- Known Exploited Vulnerabilities CatalogCISA