Taiwan Information Security Association

Security alertsSat, 14 Nov 2026

Apache HTTP Server fixes unauthenticated HTTP/2 code execution in CVE-2026-119618

An attacker who can send HTTP/2 requests to a vulnerable Apache server can corrupt memory and may execute code as the web server process. Upgrade to Apache HTTP Server 2.4.71 or the fixed vendor package. Temporarily disable HTTP/2 at the affected Apache listener if patching must wait.

01

Article

Apache HTTP Server 2.4.71, released on 11 November 2026, fixes a race condition in mod_http2 that can corrupt heap memory and allow remote code execution. Affected servers must load the vulnerable module, have HTTP/2 enabled through h2 or h2c, and accept HTTP/2 traffic from the attacker. The attack requires no account.

Check both the edge and the origin for public sites, API gateways and internal services. HTTP/2 between a browser and a CDN does not establish that Apache uses it. If the CDN forwards HTTP/1.1 to Apache, check separately for HTTP/2 on other routes such as a direct origin address, internal proxy or private listener. A successful attack runs in the web server process and could expose application files, credentials or upstream services available to that process.

Severity and exploitation status

Apache’s 11 November advisory rates the flaw Critical without publishing a numerical CVSS score. Red Hat’s CVE record reports CVSS v3.1 9.8 with low attack complexity. On 13 November, CISA’s Authorized Data Publisher added CVSS v3.1 8.1 with high attack complexity and recorded no known exploitation in its SSVC assessment. Red Hat cites public research that demonstrated exploitation on a default-configured server with the module enabled. This advisory distinguishes that demonstration from exploitation in the wild.

Attack flowHow HTTP/2 requests reach the vulnerable code
  1. 01

    Reach an Apache HTTP/2 listener

    A network path to h2 or h2c on a server with the vulnerable module loaded is required.

  2. 02

    Send concurrent requests

    A crafted series of concurrent HTTP/2 requests exercises the vulnerable header processing path without login.

  3. 03

    Corrupt memory

    A synchronization flaw in assign_headers() can cause a worker thread to overwrite shared heap memory.

  4. 04

    Execute code in the server process

    Successful exploitation can run commands with the web server process’s privileges. Connected services are at risk according to the process’s access.

Affected releases and fixes

BuildAffected version or conditionFixed release or next step
Apache HTTP Server upstream2.4.55 through 2.4.702.4.71, released 11 November 2026
Standalone mod_h22.0.8 through 2.0.42The repository is archived and lists 2.0.42 as its latest release. Use a supported fixed server build or package.
Red Hat Enterprise Linux 9 and 10Red Hat identifies affected mod_http2 packages and rates these product builds ImportantStandard channels: 2.0.26-7.el9_9.1 (RHSA-2026:98981) and 2.0.29-5.el10_3.1 (RHSA-2026:98978), respectively. Check the errata for your channel.
Red Hat JBoss Core Services 1Red Hat lists jbcs-httpd24-mod_http2 as affectedCheck the current Red Hat advisory for a channel-specific fix and use its mitigation while a fix is pending.
Ubuntu apache2 packagesRelease-specific module backports can differ from Apache’s source-version rangeFixed packages include 2.4.58-1ubuntu8.19 for 24.04 LTS and 2.4.52-1ubuntu4.27 for 22.04 LTS. Check the Ubuntu advisory for other releases.

RHEL 9 and 10 use separate allocators for HTTP/2 streams, which Red Hat says makes exploitation more difficult. Red Hat lists its RHEL 8 and earlier packages as unaffected. For packaged and embedded builds, use the vendor’s advisory and the installed package release to verify whether it contains the fix.

Response flowRecommended actions: from the perimeter to core systems
  1. 01

    Find HTTP/2 paths that reach Apache

    Inventory public and internal sites, reverse proxies, direct origin addresses, APIs, managed services, containers and embedded servers. Check the loaded module and the effective Protocols setting per listener and virtual host. Confirm what protocol each hop uses.

    See what to doResources: 1

    TWISA member solutions

    Find HTTP/2 paths that reach Apache

    Use exposure discovery to identify bypass routes to the origin. Verify the runtime module and package inventory even where the edge handles browser traffic.

  2. 02

    Patch the running server and verify its package

    Upgrade upstream installations to Apache HTTP Server 2.4.71 or a supported later release. For vendor packages, follow the security advisory for your exact release channel. Rebuild and roll out fixed container images, restart affected instances, and verify the running server actually loads the patched module.

    View guidanceResources: 3

    Response guidance

    Patch the running server and verify its package

    Upgrade upstream installations to Apache HTTP Server 2.4.71 or a supported later release. For vendor packages, follow the security advisory for your exact release channel. Rebuild and roll out fixed container images, restart affected instances, and verify the running server actually loads the patched module.

  3. 03

    Temporarily disable HTTP/2 where patching must wait

    Remove h2 and h2c from the Apache Protocols directives in scope, including virtual-host overrides, and set Protocols http/1.1. Validate the configuration, restart the relevant service using its documented procedure, and verify negotiation against the origin from an authorized network. Check client compatibility and monitor throughput and connection load.

    See what to doResources: 1

    TWISA member solutions

    Temporarily disable HTTP/2 where patching must wait

    Restrict direct origin access with firewall or network segmentation where possible. Confirm that approved ingress can still reach the origin over HTTP/1.1 and that untrusted paths cannot bypass the boundary. Apply the vendor update as soon as it is available.

  4. 04

    Investigate anomalies and recover

    Preserve edge and origin logs, crash records and process or network telemetry. Correlate suspected HTTP/2 activity with unusual worker crashes, child processes, file changes or outbound connections. If you find evidence of compromise, isolate the affected instance as appropriate, investigate reachable services and credentials, and restore from trusted artifacts.

    See what to doResources: 3

    TWISA member solutions

    Investigate anomalies and recover

    Use monitoring to correlate edge traffic with host events. Incident responders can preserve evidence and scope follow-on activity. If investigation shows the affected process could reach secrets, revoke or rotate them and review their use.

Defense architectureVerify the protocol at every hop and limit the reach of the origin

Map each hostname, virtual host, direct address, module build and protocol on both sides of the proxy.

Allow authorized traffic and apply controls at each layer.

  1. 01

    Public or internal entry

    Users, CDN and load balancer

    Know the routeIdentify how clients and proxies connect to the origin.

  2. 02

    Apache origin

    Listener, virtual host and mod_http2

    Patch and verifyInstall the fixed package and verify negotiated protocols and direct reachability.

  3. 03

    Application and data

    Backend services, file stores and credentials

    Limit accessMinimize the web process’s permissions and restrict outbound connections to required services.

Feed logs and traffic data from each layer into monitoring and response.

  1. Correlate edge and origin telemetryCompare request timing and protocols with worker crashes, processes and outbound connections.
  2. Contain and restoreIf compromise is suspected, protect evidence, contain affected instances and verify clean recovery.

Proactive testing and retesting

Within authorized scope, use asset discovery and vulnerability scans to find each listener and verify its package build. Use penetration and API tests and attack simulation in a controlled environment. Retest version, protocol negotiation and business behavior after changes. If a WAF is present, verify whether the request reached it, whether it alerted or blocked, and what the origin actually processed. Test process isolation and internal reachability separately.

TWISA member solutions

Official sources

For further product and service details, please contact the relevant TWISA members.

Advisory updated: 2026/11/14. Check the vendor’s latest information for product support and fixes.