
On November 11, 2026, the Apache Software Foundation released version 2.4.71 to address the Apache HTTP Server vulnerability. The vulnerability was independently reported by researchers who have connections with Anthropic and Google Cloud.
Among the threats they pointed out is CVE-2026-119618. It is a critical flaw in its HTTP/2 module. This vulnerability affects Apache HTTP Server versions 2.4.55 through 2.4.70. It also affects servers running the vulnerable mod_http2 module with HTTP/2 enabled.
If a remote attacker should successfully exploit this gap, they can execute code on an affected server.
The NHS England Digital security alert, published on November 12, confirmed that this is a flaw intruders are likely to exploit. This should tell you how important it is for you to patch this vulnerability immediately.
Let’s see what the Apache HTTP Server vulnerability is all about, why you should actually be worried, and what you can do to keep your systems safe.
What Is Apache HTTP Server, and How Does HTTP/2 Work?
To understand why this vulnerability is particularly concerning, it would help if we look at how Apache HTTP Server works and the role HTTP/2 plays in handling web traffic.
Apache HTTP Server is an open-source web server developed and maintained by the Apache Software Foundation. For example:
- A website’s files and resources are stored on a server.
- When someone enters the website’s address or clicks a link, their browser sends a request to the server.
- Apache HTTP Server receives and processes the request.
- It sends the requested webpage, files, or other resources back to the browser.
What about HTTP/2?
HTTP/2 is a version of the Hypertext Transfer Protocol (HTTP), which governs communication between web browsers and servers.
Unlike HTTP/1.1, HTTP/2 allows multiple requests and responses to be handled simultaneously over a single connection through a mechanism called multiplexing. This helps reduce delays and improve the efficiency of web communication.
Apache uses a module called mod_http2 to implement HTTP/2 support. The vulnerability we’re talking about exists within this module, instead of affecting every component of Apache HTTP Server.
What Is Apache HTTP Server, and How Does HTTP/2 Work?
To understand how the Apache HTTP/2 vulnerability works, let’s look at where it occurs, what causes it, and how an attacker could exploit it.
As I explained earlier, mod_http2 is the Apache module responsible for processing HTTP/2 traffic. CVE-2026-119618, on the other hand, is a race condition vulnerability involving improper synchronization when multiple execution threads access a shared resource.
A race condition occurs when multiple processes or threads access shared resources at the same time. The outcome depends on the timing or order of their operations.
For this particular vulnerability, Apache’s security advisory identifies a problem involving the assign_headers() function within mod_http2. You should be worried about this because concurrent execution means that shared memory resources will not be handled properly.
How the vulnerability can be exploited
Now, let’s take a look at how the exploitation process happens step by step:
- An attacker sends specially crafted HTTP/2 requests to a vulnerable Apache server.
- The requests trigger the race condition within the mod_http2 module.
- If it doesn’t synchronize properly, it can cause heap memory corruption.
- This memory corruption can potentially allow the attacker to execute arbitrary code on the server.
The heap here is an area of memory used by running programs to store dynamically allocated data. It gets corrupted when that memory is improperly modified or accessed, potentially affecting how the application behaves.
It is also important to note that the vulnerability can be exploited remotely without authentication. In practical terms, an attacker does not need a legitimate account or existing access to the server to attempt exploitation. They need to be able to reach the affected service over HTTP/2.
That being said, not every Apache server is automatically vulnerable. Before a server can be affected, the vulnerable module must be present and HTTP/2 must be enabled.
Which Apache HTTP Server Versions Are Affected?
You should be able to know whether your server software falls within the affected range. The Apache HTTP Server Project identifies the following affected versions:
| Component | Affected versions |
|---|---|
| Apache HTTP Server | 2.4.55–2.4.70 |
| Standalone mod_h2 | 2.0.8–2.0.42 |
NOTE: Apache HTTP Server versions 2.4.55 through 2.4.70 are affected when the vulnerable HTTP/2 functionality is enabled.
Also, the standalone mod_h2 implementation distributed through GitHub has its own affected version range. The mod_h2 repository has also been archived and is no longer receiving security updates. Any administrator relying on that implementation should consider migrating to the supported HTTP/2 implementation in Apache HTTP Server.
To be on the safe side, please make sure you check the installed version and HTTP/2 configuration. A server might run an affected Apache release but not be exposed to this specific flaw if HTTP/2 is disabled.
Likewise, if you are an administrator, don’t assume you’re safe simply because your websites use a CDN or reverse proxy. You still need to verify the configuration of the actual Apache server.
Why Remote Code Execution Is a Serious Server Security Risk
The Apache HTTP/2 vulnerability has serious consequences. In a little while, I’ll help you understand why remote code execution (RCE) is more concerning than an ordinary software bug.
What is remote code execution?
Remote code execution is a security vulnerability that allows an attacker to run commands or execute code on another computer or server from a remote location.
In the context of CVE-2026-119618, an unauthenticated attacker can use this as an avenue to execute arbitrary code on an affected Apache server. If an organization runs that server, there are three possible consequences they could face:
1. Unauthorized access to sensitive information
An attacker who successfully compromises a server could potentially access files, application data, credentials, or other sensitive information available to the compromised process.
This can in turn affect customer information, website availability, business operations, and organizational trust.
2. Unauthorized changes to server resources
Depending on the privileges of the Apache process, an attacker could modify files, interfere with applications, or use the compromised environment to carry out further malicious activities.
3. Website and service disruption
An attacker could potentially interfere with server operations, disrupt hosted websites, or affect applications that depend on the compromised infrastructure.
Now, the fact that an attacker successfully executes code does not automatically mean they have unrestricted control over the entire server. The extent of the damage depends partly on the permissions available to the Apache process and the server’s security configuration.
Yet still, even limited access can bring up opportunities for further attacks. This is especially true when the compromised server has access to other applications, databases, or internal systems.
How to Protect Your Server
If you’ve been wondering what to do if your server is affected, here are some practical steps you can follow.
A. Installing the Apache 2.4.71 Security Update
As for now, the solution to the Apache HTTP/2 Vulnerability (CVE-2026-119618) is to upgrade to version 2.4.71 or a later supported release that contains the fix. Let me walk you through the update process so you don’t get confused.
Step 1: Identify the installed Apache version.
Check which Apache HTTP Server version your system is currently running. You can use the appropriate Apache version-checking utility or your operating system’s package management tools to do this.
Step 2: Review the server configuration.
Check whether mod_http2 is loaded and whether HTTP/2 is enabled. This will help you know whether the server is exposed to the vulnerability.
Step 3: Install the security update.
Use the operating system’s official package repositories or the appropriate software vendor to get the patched version.
Sometimes, Linux distributions backport security fixes without changing the upstream version number in the way you expect. So, if you are an administrator, you should check your distribution’s security advisory instead of relying on the version string alone.
Step 4: Restart or reload and verify.
After installing the update, follow the vendor’s instructions to restart or reload Apache where required. Make sure the patched package is running and that the service is functioning correctly.
What If You Cannot Install the Update Immediately?
I know there are times when you will not be able to patch immediately. Still, I would not advise you to leave a vulnerable HTTP/2 configuration exposed while waiting for an update.
Here’s what to do if you cannot immediately upgrade the Apache installations because of compatibility concerns, maintenance schedules, or infrastructure restrictions.
The temporary mitigation
There’s a temporary mitigation recommended by NHS England Digital. You will have to disable HTTP/2 and restrict the affected Apache server to HTTP/1.1 until you can install the security update.
How to implement the mitigation
Apache administrators should review the Protocols directive in their server configuration. If the directive includes h2 or h2c, these HTTP/2 protocol identifiers should be removed, leaving HTTP/1.1 as the active protocol.
For example:
Protocols http/1.1
- h2 enables HTTP/2 over TLS.
- h2c enables HTTP/2 over an unencrypted connection.
Once you have changed the configuration, validate it and reload or restart Apache according to the procedure your environment uses.
Before you try this out, remember that disabling HTTP/2 is still a temporary solution, though. You will still have to install the security update later.

Why Regular Apache Server Updates Matter
You might have vulnerabilities in software you may not be aware of for a long period of time. Whenever you notice that researchers identify and report any flaw, developers are most likely to release security patches to address the underlying weaknesses.
However, those patches can only protect your business if you actually install them.
This particular flaw in Apache HTTP/2 can do some serious damage if you don’t take precautionary measures. So, please keep updating your server software so you can maintain a secure hosting environment.
Keep an eye on security advisories so you’re not left behind when anything new comes up. Regularly review announcements from Apache and the vendors responsible for your server operating system or hosting environment.
Always act fast when any security update is announced instead of postponing it indefinitely. Also, check your server configurations from time to time so you can spot exposed services, permissions, and other configuration settings that could introduce security risks early.
