The Apache Software Foundation has released Apache HTTP Server 2.4.71 to address a critical HTTP/2 vulnerability that could allow remote code execution. Tracked as CVE-2026-119618, the flaw affects Apache HTTP Server versions 2.4.55 through 2.4.70 and was patched in the November 11 release.
For government agencies operating public websites, resident portals, and online services, the immediate priority is to determine whether affected servers have HTTP/2 enabled. Red Hat confirms that an attacker does not need authentication to exploit an exposed, vulnerable configuration. Servers serving only HTTP/1.1 are not affected by this particular vulnerability.
The response should include agency-managed infrastructure and systems maintained by hosting providers. A website remaining available does not establish that its underlying server is secure.
Apache HTTP/2 Vulnerability: Key Facts
| Detail | Verified information |
|---|---|
| Vulnerability | CVE-2026-119618 |
| Apache severity rating | Critical |
| Affected component | mod_http2, Apache’s HTTP/2 module |
| Affected upstream versions | Apache HTTP Server 2.4.55–2.4.70 |
| Separately distributed affected module | GitHub mod_h2 versions 2.0.8–2.0.42 |
| Fixed upstream release | Apache HTTP Server 2.4.71 |
| Release date | November 11, 2026 |
| Exposure requirement | HTTP/2 enabled on an affected installation |
| Potential impact | Unauthenticated remote code execution |
Apache identifies the issue as improper synchronization of a shared resource in the module’s assign_headers() function. Its advisory credits Anthropic’s OSS Scanner and Google Cloud Vulnerability Research’s Anthony Weems and Simon Scannell with reporting the vulnerability.
What Makes This Apache Vulnerability Critical?
HTTP/2 allows multiple requests to travel over a single connection. Apache’s HTTP/2 module processes concurrent activity using worker threads.
According to Red Hat, a thread-safety flaw allows a worker thread to modify memory belonging to the connection thread through an inadequately protected shared allocator. The resulting memory corruption can enable an attacker to execute code within the Apache server process.
For an agency, the potential consequences depend on what that process can access. A compromised web server could put application files, accessible credentials, and connected services at risk. The business impact could include interrupted public services or unauthorized changes to website content.
These are potential consequences of successful exploitation, not evidence that a particular agency has been breached.
Has an Exploit Been Published?
NHS England’s published alert reports that security researchers have released a proof-of-concept exploit. Its National Cyber Security Operations Centre assesses exploitation as likely.
A published exploit demonstrates a practical attack path; it does not, by itself, establish widespread attacks or confirm that an individual server has been compromised.
Agencies should therefore prioritize remediation based on verified exposure rather than wait for evidence of an attack against their own environment.
Why Government Websites Need Immediate Attention
A public website may provide more than information. It can connect residents to permit applications, payment workflows, service requests, public records, and account-based services.
For agencies using affected Apache configurations, remediation planning should consider:
- Service availability: Which public functions would be interrupted by a server outage?
- Information access: What data and credentials can the web server process reach?
- System connections: Which internal applications or APIs depend on the affected server?
- Operational ownership: Who can patch, restart, and validate each deployment?
These questions help translate a software advisory into an actionable response.
Agencies reviewing their wider web infrastructure can also refer to our coverage of PHP2Shell vulnerabilities for government. Apache and PHP are separate components, so remediation evidence should identify which component each update addresses.
How to Check Whether Your Agency Is Affected
Review Both Software and Configuration
Begin with the installed Apache and HTTP/2 module packages, their vendor patch status, and the effective protocol configuration.
The University of Michigan recommends checking HTTP/2 settings at both the server and virtual-host levels, including Protocols entries containing h2 or h2c. It also cautions that version checks alone may not account for vendor-backported fixes.
A useful assessment record should include:
| Assessment item | Evidence to collect |
|---|---|
| Application and hostname | The service using the server |
| Responsible owner | Agency team or hosting provider |
| Installed packages | Apache and HTTP/2 module package details |
| Protocol configuration | Whether HTTP/2 is enabled |
| Reachability | Internet-facing or internally accessible |
| Vendor advisory | Applicable affected or fixed package status |
| Remediation evidence | Update, restart, and validation records |
Don't Rely on the Apache Version Number Alone
Distribution packages can differ from upstream releases.
Ubuntu specifically notes that newer HTTP/2 module versions have been backported to stable Ubuntu releases. Its advisory also lists fixed packages whose Apache version numbers remain below 2.4.71. This means a simple comparison against the upstream version range can produce an incorrect conclusion about a distribution-maintained installation.
Ask the operating system vendor or hosting provider to confirm explicitly whether the installed package addresses CVE-2026-119618.
What Government IT Teams Should Do Now
1. Prioritize Exposed, Business-Critical Services
We recommend starting with affected internet-facing systems, particularly those supporting authentication, sensitive information, or essential resident transactions.
Include vendor-managed websites, secondary deployments, and recovery environments in the review. Assign an owner and target completion time to each affected service.
2. Apply the Supported Security Update
For upstream installations, Apache HTTP Server 2.4.71 contains the fix. For distribution-maintained installations, apply the vendor’s security update addressing this CVE and verify the installed package against the advisory. The University of Michigan recommends both approaches, depending on how Apache is maintained.
Follow the vendor’s instructions for restarting affected services so that the corrected code is running. CUHK’s security advisory also calls for checking the package changelog or vendor advisory to confirm that the fix is present.
3. Temporarily Disable HTTP/2 if Patching Must Wait
NHS England recommends temporarily restricting affected servers to HTTP/1.1 where immediate patching is not possible. Its guidance specifies removing h2 and h2c from the Protocols directive, subject to compatibility and performance requirements.
Have the responsible administrator check all applicable configurations and validate the change. Record this as a temporary mitigation with an assigned patching deadline.
4. Test the Services Residents Actually Use
After remediation, we recommend testing complete user journeys, including:
- Signing in and recovering an account.
- Submitting applications and uploading documents.
- Completing payments and receiving confirmations.
- Searching records and downloading files.
- Using integrations that connect the website to other systems.
A successful homepage check provides limited assurance about the services behind it.
5. Review Suspicious Activity Separately
As part of the response, security teams should review available telemetry for unexplained process crashes, unexpected file changes, unusual child processes, or abnormal outbound connections.
These indicators are not specific proof of this exploit. Where suspicious activity is identified, follow the agency’s incident-response process. Applying a patch addresses the vulnerability; determining whether earlier compromise occurred requires a separate investigation.
What Agencies Should Ask Their Hosting Providers
A useful provider response should address the specific vulnerability and the deployed environment.
Request written confirmation of:
- Whether the service uses an affected Apache HTTP/2 implementation.
- Whether HTTP/2 is enabled on relevant servers and virtual hosts.
- Which vendor advisory and fixed package apply.
- When the update or temporary mitigation was completed.
- Whether affected services were restarted and application workflows validated.
- Whether any suspicious activity requires further investigation.
For cloud-hosted environments, clarify who maintains the operating system, web server, container image, and application. Agencies can incorporate these responsibilities into their broader government cloud infrastructure planning.
How App Maisters Government Can Help
App Maisters Government’s cybersecurity services for government agencies include vulnerability assessments, security risk evaluation, and incident-response support. Its cloud consulting services also cover infrastructure assessment, deployment, monitoring, and modernization.
Agencies evaluating this Apache vulnerability can begin with a focused review of affected applications, infrastructure ownership, remediation requirements, and post-update testing.
The immediate objective is clear: establish exposure, apply a supported fix or verified temporary mitigation, and confirm that essential public services remain operational.
Frequently Asked Questions
What is the Apache HTTP/2 vulnerability CVE-2026-119618?
CVE-2026-119618 is a critical vulnerability in Apache HTTP Server’s mod_http2 module. A flaw in how concurrent requests share memory can cause memory corruption and potentially allow an unauthenticated attacker to execute code with the web server process’s privileges. Affected servers must have HTTP/2 enabled for this vulnerability to be exploitable.
Which Apache HTTP Server versions are affected?
Apache identifies upstream versions 2.4.55 through 2.4.70 as affected, along with separately distributed GitHub mod_h2 versions 2.0.8 through 2.0.42. Distribution-maintained packages require additional verification because vendors may backport module changes or security fixes. Check the applicable vendor advisory rather than relying solely on the Apache version number.
How can I check whether my Apache server has HTTP/2 enabled?
Ask your administrator or hosting provider to review the loaded HTTP/2 module and effective Protocols settings across the main server configuration and individual virtual hosts. Entries containing h2 or h2c indicate HTTP/2 configuration. Combine this review with installed package details and vendor patch status to determine exposure.
How do I patch the Apache HTTP/2 vulnerability?
Upgrade an affected upstream installation to Apache HTTP Server 2.4.71, which contains the fix, or apply your operating system vendor’s security update for CVE-2026-119618. Follow the vendor’s restart instructions, confirm the corrected package is active, and test essential website functions after deployment.
Can disabling HTTP/2 protect my server until I install the patch?
Temporarily disabling HTTP/2 addresses the exposure condition for this vulnerability. NHS England recommends removing h2 and h2c from applicable Protocols settings and restricting affected servers to HTTP/1.1 when immediate patching is not possible. Validate compatibility and performance, and complete the supported security update as soon as possible.
Does this Apache vulnerability affect WordPress or Drupal websites?
Potentially. The determining factor is whether the website runs on an affected Apache installation with HTTP/2 enabled—not which CMS it uses. Updating WordPress, Drupal, themes, or plugins does not itself update the underlying Apache server. Ask your hosting provider to confirm that the server package includes the fix for CVE-2026-119618.



