# CVE-2026-119618: Apache HTTP Server: mod_http2: heap corruption and RCE in assign_headers

> A race in Apache HTTP Server mod_http2 header assignment can corrupt heap memory and allow remote code execution on servers using HTTP/2.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** Yes
- **Published:** 11 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** ALPINE-CVE-2026-119618, BELL-CVE-2026-119618, DEBIAN-CVE-2026-119618, ECHO-3cc1-0f38-0072, GHSA-hjhf-gpg9-qqfj, UBUNTU-CVE-2026-119618

## What is CVE-2026-119618?

CVE-2026-119618 is a race condition vulnerability in Apache HTTP Server, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Concurrent Execution using Shared Resource with Improper Synchronization vulnerability in Apache HTTP Server's mod_http2 in assign_headers() can lead to RCE.

This issue affects Apache HTTP Server: from 2.4.55 through 2.4.70.
Affected releases of mod_h2 from GitHub: from 2.0.8 through 2.0.42.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2026-119618?

Only installations with a non-default setting turned on are exposed.


## How do I fix CVE-2026-119618?

Upgrade to a fixed version.

## Is CVE-2026-119618 being exploited?

There is no known exploitation of CVE-2026-119618 in the wild and no public exploit code.

Public exploit code:

- Apache httpd mod_http2 (2.4.55-2.4.70) races on the connection allocator when assign_headers() writes the synthesised Content-Length: 0 into the shared stream table, corrupting the child heap. Containerised lab, stdlib HTTP/2 PoC, ASan and TSan evidence, 2.4.71 differential, workaround test, 0day sweep. (github_poc): https://github.com/googlesky/CVE-2026-119618
- Detection-only triage for Apache HTTP Server 2.4.71 batch: CVE-2026-119618 (mod_http2 RCE, CVSS 9.8), CVE-2026-106023, CVE-2026-109163. Grades httpd versions, catches the distro-backport and mod_h2 traps. (github_poc): https://github.com/foxcornlab/apache-httpd-scanner
- https://github.com/suominen/CVE-2026-119618 (github_poc): https://github.com/suominen/CVE-2026-119618
- Passive BigFix Apache mod_http2 CVE-2026-119618 assessment pilot; archived review snapshot. (github_poc): https://github.com/jeffschafer/Bigfix-Apache-HTTP2-Vulnerability-Scanner-CVE-2026-119618
- Independent community CLI scanners for Apache mod_http2 CVE-2026-119618 on Windows, Linux and macOS.  (github_poc): https://github.com/jeffschafer/Apache-HTTP2-RCE-HEAP-CORRUPTION-CVE-2026-119618-STAND-ALONE-SCANNER
- cve-2026-119618 (github_poc): https://github.com/geovanidps/cve-2026-119618-Apache

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119618 and fix it if it is affected.

What it is: CVE-2026-119618 is a race condition vulnerability in Apache HTTP Server, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-119618 in the wild and no public exploit code.
Exposure: Only installations with a non-default setting turned on are exposed.

Affected product: Apache HTTP Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119618/ (Markdown: https://insights.sbomify.com/CVE-2026-119618/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119618
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119618
- OSV: https://osv.dev/vulnerability/CVE-2026-119618

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119618/
Summaries are generated and may contain mistakes; the official description above is the record.