Apache mod_http2 CVE-2026-119618: Reported Active Exploitation; Upstream Fixed in 2.4.71

Singapore’s CSA says CVE-2026-119618 is reportedly being actively exploited. Apache HTTP Server 2.4.55–2.4.70 is affected when mod_http2 is enabled; upstream fixed it in 2.4.71.

Reader ratingRate this article

Loading reader rating…

Privacy-conscious voting uses a signed random browser identifier and a short-lived network hash; the rating tables contain no raw IP-address column.

Reader ratings require JavaScript; the article remains fully readable without it.

Apache HTTP Server security update

Decision: Treat CVE-2026-119618 as an urgent patching issue when Apache HTTP Server 2.4.55 through 2.4.70 runs with mod_http2 enabled. Apache fixed the upstream flaw in 2.4.71.[1][2]

Exploitation status: Singapore’s Cyber Security Agency says the vulnerability is reportedly being actively exploited and that a proof of concept is publicly available.[2]

Reporting cutoff: November 18, 2026, 6:56 a.m. EST / 11:56 UTC.

Affected upstreamApache HTTP Server 2.4.55 through 2.4.70.[1]
Exposure conditionOnly servers with HTTP/2 enabled are affected; HTTP/1.1-only servers are not vulnerable.[3]
Fixed upstreamApache HTTP Server 2.4.71, released November 11.[1]

What changed since November 12

CSA published its alert on November 17 and says CVE-2026-119618 is reportedly being actively exploited; it also says a proof-of-concept exploit is publicly available.[2]

The CISA Known Exploited Vulnerabilities JSON feed checked for this article—catalog version 2026.11.17, released November 17 at 17:53 UTC—contained zero exact matches for CVE-2026-119618.[4]

Evidence boundary: absence from that named CISA feed snapshot does not disprove CSA’s qualified report; it means the two official surfaces did not provide the same catalog signal at the cutoff.[2][4]

Technical and version scope

Apache describes an improper-synchronization flaw in mod_http2’s assign_headers() that can lead to remote code execution.[1] Red Hat says a reachable, unauthenticated attacker could execute arbitrary commands when HTTP/2 is enabled.[3]

Component or product context Reviewed status What controls the decision
Upstream Apache HTTP Server 2.4.55 through 2.4.70 affected; 2.4.71 fixed.[1] Apache’s advisory.
Standalone mod_h2 from GitHub 2.0.8 through 2.0.42 affected.[1] The source and build that control that deployment.
Red Hat Enterprise Linux Red Hat rates RHEL 9 and 10 Important rather than Critical and says RHEL 8 and earlier are not affected.[3] Red Hat’s product-specific assessment and affected-package information.

Do not judge a vendor package by the upstream-looking version alone

Red Hat says it usually backports fixes to older package versions instead of rebasing to entirely new versions, so scanners that consider only the package version can report a fixed or unaffected package as vulnerable.[3]

Practical guidance — bounded editorial inference: for distribution, appliance, hosting-panel, and managed-service builds, use the controlling vendor’s advisory and fixed-build record rather than requiring the upstream 2.4.71 string everywhere.[1][3]

What to do now

  1. Practical guidance — inventory the exact deployment. Record the Apache package source, installed build, standalone mod_h2 version if applicable, and whether HTTP/2 is enabled. This is an exposure check, not a finding that the server is compromised.[1][3]
  2. Confirm the feature condition. Use the server or controlling vendor’s supported inspection method to determine whether HTTP/2 is enabled; do not infer exposure from the presence of Apache alone.[2][3]
  3. Apply the controlling source’s fixed build. Apache identifies 2.4.71 as the upstream fix, while CSA advises affected users and administrators to update to the latest versions immediately.[1][2]
  4. Validate the downstream result. For vendor packages, confirm the installed build against that vendor’s security record because backported fixes can retain an older upstream-looking version.[3]
  5. Activate and verify every running instance. Follow the controlling vendor or platform procedure rather than a universal command.[3] For upstream Apache, a graceful restart replaces children with a new generation; confirm the remediated binary is serving and old-generation children have drained.[5] For Kubernetes deployments, require rollout completion: all replicas updated and available, with no old replicas running.[6]

What remains unknown

As of the cutoff, the four reviewed vulnerability-status surfaces do not provide victim identities or counts, indicators of compromise, campaign scale, or actor attribution.[1][2][3][4]

CSA’s wording is “reportedly being actively exploited.” This article therefore does not claim a verified victim count, a confirmed campaign, or universal compromise of exposed servers.[2]

Sources

  1. Apache HTTP Server 2.4 vulnerabilities — CVE-2026-119618 (accessed November 18, 2026).
  2. Cyber Security Agency of Singapore alert AL-2026-164 (published November 17, 2026; accessed November 18, 2026).
  3. Red Hat CVE-2026-119618 (accessed November 18, 2026).
  4. CISA Known Exploited Vulnerabilities catalog JSON (catalog version 2026.11.17; accessed November 18, 2026).
  5. Apache HTTP Server 2.4 — Stopping and Restarting (accessed November 18, 2026).
  6. Kubernetes — Deployments (accessed November 18, 2026).