CVE-2026-119618·Apache vulnerability
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.
- Severity
- high
- Software
- Apache
- Fixed in
- 2.4.71
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 1.3% — higher than 72% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Affected versions
From: 2.4.55
Until: 2.4.71
Fixed in: 2.4.71
How to fix this CVE
Upgrade Apache HTTP Server to version 2.4.71 or later to patch a critical race condition in mod_http2's header assignment logic that could allow remote code execution. Organizations running versions 2.4.55 through 2.4.70 should prioritize this update, particularly for production HTTP/2 deployments. Verify the fix by confirming the installed version matches or exceeds 2.4.71.
sudo dnf update httpdDefensia detects this vulnerability
WAF mitigation (if patching is not yet possible)
Add this rule to your WAF to block exploitation attempts while you schedule the patch.
Disable or restrict HTTP/2 at the WAF level if HTTP/1.1 is sufficient for your use case, or implement request rate-limiting on HTTP/2 streams to reduce concurrent header processing load until patching is completed.How to check if you are affected
- Step 1: Check installed Apache version with: apache2ctl -v (Ubuntu/Debian) or httpd -v (RHEL/CentOS)
- Step 2: Verify mod_http2 is enabled by running: apache2ctl -M | grep http2 or httpd -M | grep http2
- Step 3: Search access and error logs for HTTP/2 requests with malformed or concurrent header assignments in the timeframe before patching: grep -i 'http/2' /var/log/apache2/access.log /var/log/apache2/error.log
- Step 4: After patching, re-run apache2ctl -v or httpd -v and confirm the version is 2.4.71 or higher
FAQ
What is CVE-2026-119618?
This vulnerability is a race condition in Apache's mod_http2 module where concurrent HTTP/2 requests can trigger improper synchronization during header processing, potentially leading to remote code execution on affected systems.
Is CVE-2026-119618 being actively exploited?
According to CISA's Known Exploited Vulnerabilities (KEV) catalog, CVE-2026-119618 is not currently documented as actively exploited in the wild, and no public exploits are available at this time.
What versions of Apache are affected by CVE-2026-119618?
Apache HTTP Server versions 2.4.55 through 2.4.70 are vulnerable. The mod_h2 GitHub repository also lists affected versions from 2.0.8 through 2.0.42.
How do I check if my server is vulnerable to CVE-2026-119618?
Run 'apache2ctl -v' or 'httpd -v' and verify your version. If it falls between 2.4.55 and 2.4.70 (inclusive) and 'apache2ctl -M | grep http2' or 'httpd -M | grep http2' shows mod_http2 is loaded, your system is vulnerable.
Does Defensia detect CVE-2026-119618?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Apache is installed on a monitored server, CVE-2026-119618 will appear in your dashboard with remediation steps.
Related Apache CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-119618. Free for 1 server.
Get started free