Security advisory · Server software

CVE-2026-119618: a vulnerability in the Apache HTTP Server

Updated November 18, 2026By HostCrust2 min read

CVE-2026-119618 in the Apache HTTP Server's mod_http2 allows remote attackers to achieve RCE due to improper synchronization in assign_headers(), affecting versions from 2.4.55 through 2.4.70; fixed in 2.4.71. Prioritise any internet-facing service first. The affected versions, the fix and the CVSS score below come straight from the CVE record, not our interpretation.

CVE ID
CVE-2026-119618
Published
November 11, 2026
CVSS
8.1 (High), CVSS 3.1
Affected
from 2.4.55 up to the fixed release
Fixed in
2.4.71
Assigned by
Apache

What is CVE-2026-119618?

CVE-2026-119618 is a Concurrent Execution using Shared Resource with Improper Synchronization vulnerability in the Apache HTTP Server's mod_http2 implementation. The flaw exists in the assign_headers() function, where shared data can be accessed concurrently without proper synchronization, enabling a remote attacker to manipulate state and achieve remote code execution (RCE). The issue affects Apache HTTP Server releases from 2.4.55 through 2.4.70 and affected releases of mod_h2 from GitHub from 2.0.8 through 2.0.42. The attack vector is network-based (remote) and does not require user interaction; exploitability is increased where multiple requests or streams race on shared structures in mod_http2. The impact includes high severity compromise — confidentiality, integrity, and availability can be fully impacted by successful RCE. The defect is addressed in the fixed release 2.4.71, which corrects the improper synchronization in assign_headers(). The affected and fixed versions, the CVSS score and the remediation below are taken directly from the CVE record and the vendor advisory linked under Sources, not from our interpretation.

Am I affected?

Affected: the Apache HTTP Server from 2.4.55 up to the fixed release (through 2.4.70). Also affected are mod_h2 releases from GitHub from 2.0.8 through 2.0.42. Fixed in 2.4.71.

How do I fix it?

Install your distribution's security update for this package, then restart the affected service so the running process picks up the fix.

# Debian / Ubuntu
sudo apt update && sudo apt upgrade

# RHEL / AlmaLinux / Rocky Linux
sudo dnf upgrade --refresh

How HostCrust helps you see it

Patch Proof checks the packages on each server against your distribution's own security data, per CVE, so once your distribution publishes its fix it shows this package as open until the update is installed — and because it is a running service, the fix isn't done until you restart it.

How we checked this: Every fact on this page — the CVE id, the affected and fixed versions, the CVSS score and the remediation — was taken from the NVD record and the vendor advisory linked under Sources, and checked on November 18, 2026. HostCrust did not independently reproduce the vulnerability. Anything we didn't run ourselves comes from the official documentation listed under Sources.

Check which CVEs are really open on your server

HostCrust Patch Proof compares every installed package with your distribution's own security data. It counts fixes your distro backported and checks the kernel that is actually running, not just the one on disk. Read-only, no root, free.

Run the free check About Patch Proof

FAQ

How severe is CVE-2026-119618?

The NVD record lists a CVSS base score of 8.1 (High) (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H). Severity scores can be revised as a CVE is analysed, so check the NVD record and the vendor advisory under Sources for the current figure.

How do I fix it?

Install your distribution's or vendor's fixed release for the Apache HTTP Server and restart the affected service (or reboot, for a kernel fix). The commands are in the section above.

Where do these facts come from?

Every fact on this page is copied from the NVD record and the vendor advisory linked under Sources. HostCrust reformats the official facts; it does not add its own.

Sources

  1. NVD: CVE-2026-119618
  2. Vendor advisory: httpd.apache.org
  3. Vendor advisory: github.com
  4. Reference: access.redhat.com
  5. Reference: bugs.gentoo.org