Apache HTTP Server CVE-2026-119618 (mod_http2): Fixed Versions

On November 11, 2026, Apache HTTP Server 2.4.71 fixed three vulnerabilities. The most serious, CVE-2026-119618, is a race condition in the HTTP/2 module, mod_http2, that Apache rates critical and says can lead to remote code execution. Apache lists httpd 2.4.55 through 2.4.70 as affected, plus releases 2.0.8 through 2.0.42 of the standalone mod_h2 module from GitHub. Only servers with HTTP/2 turned on are exposed to this flaw. On November 17, Singapore’s Cyber Security Agency said the flaw “is reportedly being actively exploited, and a proof-of-concept exploit is publicly available.” As of November 20, it is not in CISA’s Known Exploited Vulnerabilities catalog.

Find your fixed version
By CalMax Systems Security Research · Published November 20, 2026 · Last updated: November 20, 2026

What is CVE-2026-119618, and which version fixes it?

CVE-2026-119618 is a flaw in the assign_headers() function of Apache’s mod_http2 module. Apache classes it as a race condition (CWE-362) that can lead to remote code execution and rates it critical. Upgrade to Apache HTTP Server 2.4.71, or install your distribution’s fixed package. The standalone mod_h2 project on GitHub is archived and has no fixed release, so move to the mod_http2 that ships with httpd 2.4.71. The same release fixes CVE-2026-106023 (important, mod_md) and CVE-2026-109163 (low, mod_vhost_alias).

As of November 20, 2026, none of the three CVEs is in CISA’s Known Exploited Vulnerabilities catalog (version 2026.11.20), and CISA’s November 13 assessment for CVE-2026-119618 records exploitation as none. On November 17, however, Singapore’s Cyber Security Agency said the flaw “is reportedly being actively exploited, and a proof-of-concept exploit is publicly available.” Patch exposed systems now and check them for signs of compromise. Red Hat says public research has demonstrated a reliable exploit against a default-configured server with the mod_http2 module enabled. Apache publishes no workaround. Until you can patch, Red Hat recommends removing HTTP/2 from the Protocols directive (see below).

Fixed Versions for CVE-2026-119618

From the Apache HTTP Server 2.4 security page, the CVE record and the vendor trackers listed below. Find the row for the build you run.

Product Vulnerable Upgrade to
Apache HTTP Server 2.42.4.55 through 2.4.702.4.71 or later
Apache HTTP Server before 2.4.55Not in Apache’s range for CVE-2026-1196182.4.71 anyway. Apache lists 2.4.30 through 2.4.70 as affected by CVE-2026-106023. Distributions also backport newer mod_http2 code into older httpd versions (see the Ubuntu note below), so check your vendor’s tracker.
Standalone mod_h2 from GitHub2.0.8 through 2.0.42No fixed standalone release. The icing/mod_h2 repository is archived, its last release is v2.0.42 (May 29, 2026), and its README says the module is now maintained as part of Apache httpd. Use the mod_http2 included with httpd 2.4.71, or a vendor package with the fix.
Red Hat Enterprise Linux 10mod_http2 packagemod_http2-2.0.29-5.el10_3.1 (RHSA-2026:98978)
Red Hat Enterprise Linux 9mod_http2 packagemod_http2-2.0.26-7.el9_9.1 (RHSA-2026:98981)
Red Hat Enterprise Linux 8 and earlierNot affected (Red Hat)No action needed for this CVE
Red Hat JBoss Core Servicesjbcs-httpd24 packagesRHSA-2026:100550 (RHEL 8 packages, including jbcs-httpd24-mod_http2-2.0.29-16.el8jbcs) or RHSA-2026:100552 (JBoss Core Services 2.4.62.SP7)
One upgrade covers the whole release. Apache HTTP Server 2.4.71 fixes all three CVEs. On Red Hat, the CVE-2026-119618 fix ships in the separate mod_http2 package, while CVE-2026-106023 is in the httpd package, which Red Hat still listed as affected with no fix on November 20 (details below). If you run an extended-support stream, use its own erratum: RHEL 9.4 E4S (RHSA-2026:98968, mod_http2-2.0.26-2.el9_4.4), 9.6 EUS (RHSA-2026:98954, mod_http2-2.0.26-4.el9_6.3), 9.8 EUS (RHSA-2026:98982, mod_http2-2.0.26-6.el9_8.3), 10.0 EUS (RHSA-2026:98953, mod_http2-2.0.29-2.el10_0.3) and 10.2 EUS (RHSA-2026:98979, mod_http2-2.0.29-4.el10_2.3).

Linux distribution packages (checked November 20, 2026)

Distributions often backport the fix into their own package, so the version httpd -v prints may not change. Compare the full package version with your distribution’s tracker.

  • Ubuntu: CVE-2026-119618 is fixed in apache2 2.4.68-1ubuntu6.2 (26.10), 2.4.66-2ubuntu2.8 (26.04 LTS), 2.4.58-1ubuntu8.19 (24.04 LTS) and 2.4.52-1ubuntu4.27 (22.04 LTS), and through Ubuntu Pro in 2.4.41-4ubuntu3.23+esm11 (20.04 LTS). Ubuntu lists 18.04, 16.04 and 14.04 as not affected. Ubuntu notes that newer versions of the module have been backported to its stable releases, which is why 22.04 and 20.04 need the fix even though their httpd versions are older than 2.4.55. The same package versions fix CVE-2026-106023 and CVE-2026-109163, and Ubuntu also lists CVE-2026-109163 fixes for 18.04, 16.04 and 14.04 through Ubuntu Pro.
  • Debian: all three CVEs are fixed in apache2 2.4.71-1~deb13u1 for Debian 13 trixie (DSA-6620-1), 2.4.71-1~deb12u1 for Debian 12 bookworm (DLA-4902-1) and 2.4.71-1 for testing (forky) and unstable.
  • Red Hat: rates CVE-2026-119618 Critical overall and Important for RHEL 9 and 10, because Red Hat’s mod_http2 packages there give each HTTP/2 stream its own allocator, which it says “substantially increases the complexity of exploiting the flaw.” Fixed packages for RHEL 9, RHEL 10 and JBoss Core Services are in the table above, and RHEL 8 and earlier are not affected. Red Hat lists the Red Hat OpenShift GitOps console plugin as affected with no fix yet. For CVE-2026-106023, Red Hat lists httpd in RHEL 8, 9 and 10 and JBoss Core Services as affected with no fixed package. Red Hat lists RHEL 6 and 7 as unaffected and Red Hat Hardened Images as fixed under RHSA-2026:98998. (Red Hat’s CVE page; its VEX file lists RHEL 8 as not affected, so check the page for updates if you run mod_md on RHEL 8.) For CVE-2026-109163, Red Hat lists RHEL and JBoss Core Services as not affected, and says standard configurations without mod_vhost_alias directives are unaffected.

For any other distribution, or for a product that bundles httpd, check that vendor’s security tracker.

What CVE-2026-119618 Does

Neither finder has published a write-up that we could find, so these details come from the Apache advisory and Red Hat’s bulletin RHSB-2026-017.

Apache describes CVE-2026-119618 as a “Concurrent Execution using Shared Resource with Improper Synchronization vulnerability in Apache HTTP Server’s mod_http2 in assign_headers() [that] can lead to RCE.” Its title for the issue is “heap corruption and RCE in assign_headers.” The fix is Apache commit 824beab in the 2.4.x branch.

Red Hat explains it in more detail. HTTP/2 lets one connection carry many requests at once, and mod_http2 handles them with multiple threads. Because of a thread-safety flaw, a worker thread can write into memory owned by the connection thread through a shared allocator that lacks adequate locking. Red Hat says a remote attacker can trigger this with a crafted sequence of concurrent HTTP/2 requests and run arbitrary code in the context of the httpd server process, with no authentication.

Who is exposed: Red Hat lists three conditions: httpd is running with mod_http2 loaded, a Protocols directive includes h2 or h2c, and an attacker can reach the server. Apache’s documentation says Apache’s built-in default is Protocols http/1.1, but distribution packages and enabled module configs can turn HTTP/2 on, so check the active configuration rather than assuming it is off. Red Hat says servers that serve only HTTP/1.1 are not vulnerable.

Severity: Apache rates it critical and publishes no CVSS score. CISA’s entry in the CVE record, which NVD also shows, scores it 8.1 (High) under CVSS 3.1 with high attack complexity. Red Hat scores it 9.8 with low attack complexity.

Who found it: Apache credits Anthropic’s OSS Scanner (as vulnerability ANT-2026-MAPKT6MZ), which reported it on October 26, 2026, and Google Cloud Vulnerability Research, which reported it on November 3.

All Three CVEs in Apache HTTP Server 2.4.71

Descriptions, severity and affected ranges from Apache. CVSS 3.1 scores from CISA’s entry in each CVE record. Mitigations from Red Hat, because Apache lists none.

CVE What it is Affected (Apache) Apache severity CVSS 3.1 (CISA) Mitigation Red Hat lists
CVE-2026-119618mod_http2: heap corruption and remote code execution in assign_headers2.4.55 to 2.4.70; mod_h2 2.0.8 to 2.0.42Critical8.1Remove h2 and h2c from every Protocols directive
CVE-2026-106023mod_md: NULL pointer dereference during HTTP request processing that crashes a child process2.4.30 to 2.4.70Important7.5If you do not need automatic ACME certificate management, stop loading mod_md and restart httpd. Certificates must then be managed another way.
CVE-2026-109163mod_vhost_alias: 1-byte stack buffer overwrite2.4.69 and 2.4.70Low5.9If you do not need dynamic mass virtual hosting, stop loading mod_vhost_alias and restart httpd. This breaks VirtualDocumentRoot and VirtualScriptAlias setups.
About the ranges. In the CVE records for CVE-2026-106023 and CVE-2026-109163, the description text ends at 2.4.69, while the affected-version data in the same records and Apache’s security page include 2.4.70. Either way, 2.4.71 is the fixed release. Apache’s title for CVE-2026-109163 says it comes “after CVE-2026-63292,” an earlier mod_vhost_alias stack overflow that Apache fixed in 2.4.69. Red Hat says CVE-2026-106023 can crash worker processes but cannot lead to code execution, and that CVE-2026-109163 only matters where mod_vhost_alias directives such as VirtualDocumentRoot are configured.

How to Check Your Version and Exposure

These checks use the httpd options in Apache’s documentation and the detection steps in Red Hat’s bulletin. Run them on each server that runs Apache httpd.

1. Find the version

httpd -v        # Red Hat and most source builds
apachectl -v
apache2 -v      # Debian and Ubuntu

Apache lists 2.4.55 through 2.4.70 as affected by CVE-2026-119618 and 2.4.71 as fixed. A distribution package can carry the fix under an older version number, and Ubuntu has backported the affected module code into older versions, so also check the full package version against your distribution’s tracker (see the list above). On RHEL 9 and 10, mod_http2 is its own package:

rpm -q httpd mod_http2

2. Check whether mod_http2 is loaded

apachectl -M 2>/dev/null | grep -i http2
apache2ctl -M 2>/dev/null | grep -i http2   # Debian and Ubuntu

http2_module in the output means mod_http2 is loaded. proxy_http2_module is a different module, mod_proxy_http2, which handles HTTP/2 connections to backends. Apache’s advisory names only mod_http2. No output means the module is not loaded, or the command did not run, so make sure apachectl -M on its own prints the module list for the server your service actually starts.

3. Check whether HTTP/2 is turned on

sudo grep -rniE '^[[:space:]]*Protocols[[:space:]]' /etc/httpd/ /etc/apache2/ 2>/dev/null

Red Hat says a Protocols line that includes h2 (HTTP/2 over TLS) or h2c (HTTP/2 over cleartext) means HTTP/2 is on. Apache’s documentation says Protocols can be set for the whole server and for each virtual host, so inspect the complete directive for every match, including any lines continued with a trailing backslash. Where no Protocols directive applies, the default is Protocols http/1.1. No output from this search is not proof on its own: Apache’s documentation says the main configuration file can pull in other files with the Include directive, so also search any included files that live elsewhere, for example under a hosting control panel’s own directory.

4. Check whether HTTP/2 answers

Red Hat gives this check. Replace HOST with your hostname, and run it from outside your network as well as on the server:

curl -kI --http2 https://HOST/

Read the protocol on the server’s response and ignore any proxy 200 Connection established line. An HTTP/2 response confirms that HTTP/2 was negotiated. An HTTP/1.1 response shows what this request negotiated. The server can prefer HTTP/1.1 even when HTTP/2 is enabled, so confirm the active configuration in step 3. The result covers only that hostname and port, so check each TLS virtual host you run. Your curl must support HTTP/2 (curl -V lists HTTP2 under Features). This tests TLS only, not cleartext h2c, so rely on step 3 for that. If a CDN or reverse proxy sits in front of httpd, this tests the proxy, so run it against the httpd server directly too.

Apache httpd also ships inside other products. Red Hat says any Red Hat product that relies on a RHEL httpd or mod_http2 package is potentially affected, and lists Red Hat JBoss Core Services and the Red Hat OpenShift GitOps console plugin. Appliances, hosting control panels and container images from other vendors can bundle httpd too, and their version numbers may not match Apache’s. Check each vendor’s advisory for its fixed build or workaround. Axis’s November 16 advisory lists AXIS OS 6.50.5.10 and later as affected. While awaiting the device software update, follow the advisory to disable both AllowH2 and AllowH2c in the device’s HTTP/2 settings. For example, Broadcom’s VMSA-2026-0010 (November 19) lists VMware Cloud Foundation Operations 9.x, standalone VMware Aria Operations 8.18.x, VMware Aria Operations bundled with VMware Cloud Foundation 5.x, and VCF Operations HCX 9.1.x as affected, with patches pending. For Operations, follow KB463005 on every affected node. Upgrades can restore the vulnerable HTTP/2 configuration, so reapply the workaround on every node after each upgrade until you install a fixed Operations release. For HCX Manager, follow KB463022 and verify HTTP/2 is disabled on both ports 443 and 9443. Broadcom’s separate Tanzu advisory TNZ-2026-1105 covers affected Tanzu buildpacks and tiles, Tanzu Application Service, VMware Distributed Apache HTTPD, and Bitnami Secure Images. Broadcom lists fixed versions for the PHP Cloud Foundry buildpack (5.0.15), PHP Cloud Native buildpack (6.4.1), Web Servers Cloud Native buildpack (2.1.1), Extended App Support buildpacks (0.95.0), Extended App Support Tile (1.2.12), and Cloud Native Buildpacks Tile (0.6.16). Use the rebuilt Bitnami Secure Images for Matomo 5.14.2, phpMyAdmin 5.2.3 and WordPress 7.1.4. The advisory lists fixes as pending for Tanzu Application Service and VMware Distributed Apache HTTPD. For affected deployments awaiting a fix, follow Broadcom’s HTTP/2 workaround and restart httpd.

Fixing It

Apache lists no workaround for any of the three CVEs. Upgrading is the fix.

Upgrade, then restart

Install Apache HTTP Server 2.4.71 or your distribution’s fixed package. On RHEL 9 and 10, that includes the updated mod_http2 package. Restart the service that runs the patched Apache instance, then confirm its package version with step 1. For standard RHEL httpd, Red Hat’s bulletin uses systemctl restart httpd. For JBoss Core Services installed from RPMs and managed by systemd, Red Hat documents systemctl restart jbcs-httpd24-httpd.service. Use the service for your installation after applying the HTTP/2 workaround as well. If you built the standalone mod_h2 module from GitHub, remove it and use the mod_http2 that ships with httpd 2.4.71, because the standalone project has no fixed release.

Until you can upgrade: turn off HTTP/2 (Red Hat’s mitigation)

Apache publishes no workaround. Red Hat’s bulletin recommends removing HTTP/2 from the Protocols directive so the server serves HTTP/1.1 only:

  • Edit each Protocols line found in step 3 and remove h2 and h2c, leaving:
    Protocols http/1.1
  • Restart httpd. Red Hat’s command is systemctl restart httpd.
  • Verify with the curl check in step 4: the server’s response should use HTTP/1.1. Confirm the active configuration as well, since this result alone cannot establish that HTTP/2 is disabled. Run the search in step 3 again; no active Protocols line should contain h2 or h2c. Red Hat’s server-side check goes one step further and expects the lines that load the HTTP/2 modules (grep http2 /etc/httpd/conf.modules.d/*.conf on RHEL) to be commented out. That grep also matches mod_proxy_http2, which handles HTTP/2 connections to backends.

The trade-off: Red Hat says browsers and API clients fall back to HTTP/1.1 automatically, but page loads can be slower and bandwidth use higher without HTTP/2 multiplexing and header compression. Turn HTTP/2 back on after you upgrade.

What it does not cover: this covers only CVE-2026-119618. For CVE-2026-106023 and CVE-2026-109163, Red Hat’s module-specific mitigations are in the last column of the table above.

Check for Signs of Compromise

The Apache and Red Hat advisories give no indicators of compromise for this CVE, so the checks below are general triage.

What to look for

If you find activity you cannot explain, start your incident response process, preserve logs before making changes, and patch.

Timeline

DateEvent
September 29, 2026CVE-2026-106023 (mod_md) is reported to the Apache security team.
October 5, 2026CVE-2026-109163 (mod_vhost_alias) is reported.
October 26, 2026Anthropic’s OSS Scanner reports CVE-2026-119618 to the Apache security team.
November 3, 2026Google Cloud Vulnerability Research reports CVE-2026-119618.
November 11, 2026Apache releases httpd 2.4.71 and announces the three CVEs on the oss-security mailing list. The CVE records go live. Red Hat publishes fixed mod_http2 packages for RHEL 9 and 10.
November 12, 2026Red Hat publishes bulletin RHSB-2026-017 with the HTTP/2 mitigation.
November 13, 2026CISA’s assessment in the CVE-2026-119618 record lists exploitation as none.
November 16, 2026Axis publishes an advisory for AXIS OS 6.50.5.10 and later, with an HTTP/2 workaround.
November 17, 2026Red Hat publishes RHSA-2026:100550 and RHSA-2026:100552 for JBoss Core Services.
November 17, 2026Singapore’s Cyber Security Agency says CVE-2026-119618 is reportedly being actively exploited and a proof-of-concept exploit is publicly available.
November 19, 2026Broadcom publishes VMSA-2026-0010 for VMware products that bundle httpd, with patches pending and workarounds available.
November 20, 2026None of the three CVEs is in CISA’s Known Exploited Vulnerabilities catalog (version 2026.11.20).

Where ThreatListPro Fits

A blocklist does not fix this flaw. Patching does.

Red Hat says any client that can reach an affected server’s HTTP/2 port can attempt CVE-2026-119618, with no login. No list of known attacker addresses can stop a new address from sending the attack. Upgrade Apache httpd, or install your distribution’s fixed package.

ThreatListPro is built for a different job: keeping known VPN attackers away from your login pages. It covers 5.4M+ IPv4 addresses and is checked for new attackers every 6 hours. Its entries come from real attacks on live production Palo Alto GlobalProtect VPN portals in the US. A firewall deny rule that uses it can reduce scanning and login attempts from listed addresses on your VPN portal and other remote-access services. See how to block IP addresses at the firewall for the supported firewalls.

Apache CVE-2026-119618 FAQs

Which Apache version fixes CVE-2026-119618?

Apache HTTP Server 2.4.71, released on November 11, 2026. Apache lists 2.4.55 through 2.4.70 as affected, plus releases 2.0.8 through 2.0.42 of the standalone mod_h2 module from GitHub. The standalone mod_h2 project is archived and has no fixed release, so use the mod_http2 that ships with httpd 2.4.71. Distribution packages often backport the fix without changing the version that httpd -v prints, so check your distribution's security tracker. On RHEL 9 and 10, the fix is in the separate mod_http2 package.

Is CVE-2026-119618 being exploited?

Singapore's Cyber Security Agency said on November 17, 2026 that CVE-2026-119618 is reportedly being actively exploited and that a proof-of-concept exploit is publicly available. CISA's November 13 assessment in the CVE record listed exploitation as none. As of November 20, the CVE is absent from CISA's Known Exploited Vulnerabilities catalog (version 2026.11.20). Red Hat says public research has demonstrated a reliable exploit against a default-configured server with the mod_http2 module enabled.

Am I affected if HTTP/2 is not enabled?

Not by CVE-2026-119618. Red Hat says only servers with HTTP/2 enabled through the Protocols directive (h2 or h2c) and mod_http2 loaded are affected, and Apache's documentation says the default is Protocols http/1.1. The same release fixes CVE-2026-106023 in mod_md, which Apache lists for 2.4.30 through 2.4.70 and which has nothing to do with HTTP/2, so upgrade even if HTTP/2 is off.

Is there a workaround for CVE-2026-119618?

Apache publishes no workaround, and upgrading to 2.4.71 is the fix. Until you can upgrade, Red Hat recommends removing h2 and h2c from every Protocols directive so the server serves HTTP/1.1 only (Protocols http/1.1), then restarting httpd. Red Hat says browsers and API clients fall back to HTTP/1.1 automatically, but page loads can be slower and bandwidth use higher. This covers only CVE-2026-119618, not the other two CVEs in the release.

What is the CVSS score for CVE-2026-119618?

Apache rates it critical and publishes no CVSS score. CISA's entry in the CVE record, which NVD also shows, scores it 8.1 (High) under CVSS 3.1 with high attack complexity. Red Hat scores it 9.8 with low attack complexity, and rates it Important rather than Critical for RHEL 9 and 10 because its mod_http2 packages there give each HTTP/2 stream its own allocator. The CISA and Red Hat vectors both describe a network attack that needs no privileges and no user interaction.

Who found CVE-2026-119618?

Apache credits Anthropic's OSS Scanner, which reported it as ANT-2026-MAPKT6MZ on October 26, 2026, and Google Cloud Vulnerability Research, which reported it on November 3. Neither has published a write-up that we could find, so the technical details on this page come from the Apache advisory and Red Hat.

Does the blocklist protect my Apache server from CVE-2026-119618?

No. Any client that can reach an affected server's HTTP/2 port can attempt the attack, and a list of known attacker addresses cannot stop a new address. Patching is the fix. ThreatListPro blocks known VPN attackers at the firewall, which can reduce scanning and login attempts on your VPN portal and other remote-access services.

Sources

Run a VPN Portal Too?

ThreatListPro blocks known VPN attackers at the firewall: 5.4M+ IPv4 addresses, checked for new attackers every 6 hours. Monthly is $19.99 with a 14-day free trial, cancel anytime before it ends at no charge.

Start a 14-day free trial Or test the free sample first: free, no signup

Firewall Guides

ThreatListPro uses a plain-text feed for firewalls that support external IPv4 address lists.

Palo Alto FortiGate pfSense OPNsense SonicWall Cisco ASA Sophos XG UniFi

Related Resources

Other internet-facing flaws we track, and how to block known attackers at the edge.

All Security Alerts NGINX HTTP/2 CVE-2026-123007 (NGINX2Root): Fixed Versions OpenSSH CVE-2026-123158: Who Is Affected? Block an IP Address at the Firewall VPN Brute Force Explained Password Spraying on VPNs