CVE-2026-119618: CVE-2026-119618: Concurrent Execution using Shared Resource with Improper Synchronization vulnerability in …

CVE-2026-119618 at a glance

CVE-2026-119618 is a Race Condition vulnerability in Concurrent Execution. NVD published it on 2026-11-11 and classifies the weakness as CWE-362. Public exploit code: 13 public GitHub proof-of-concept repositories from 12 accounts, with the earliest exploit evidence dated 2026-11-12. FIRST EPSS puts the probability of exploitation activity in the next 30 days at 1.33% (percentile 71.5, scored 2026-11-14). NVD does not list a fixed version, so the vendor advisory is the reference for the fix. Its CVERadar threat level is 29/100.

What it is

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.

Exploitation evidence

First exploit evidence seen: 2026-11-12 (earliest date across the sources below).

Exploited in the wild

No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).

Public exploit code

GitHub proof-of-concept repositories

13 public repositories from 12 accounts, first seen 2026-11-12. Most starred: googlesky/CVE-2026-119618 (10 stars), view the googlesky/CVE-2026-119618 repository on GitHub.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: nomi-sec/PoC-in-GitHub.

Patches, mitigations and detection

Fixed versions

NVD does not list a fixed version for this CVE. Use the vendor advisory below.

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

No vendor-tagged reference yet; see the full reference list.

Detection Generic guidance

Response checklist Generic guidance

1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

Before patching, it helps to know every exposed instance; external attack surface monitoring from LayerLogix does that inventory.