Daily · Article 01 · 4 min read
- Security
- Open source
Apache fixes a critical HTTP/2 flaw. Which package does your server need?
Apache release dated November 11 · vendor advisories checked November 13 JST
Summary
Apache has fixed a critical flaw in its HTTP/2 component. Here is why the upstream and operating-system packages can carry different numbers and what shows that the fix is running.
Key facts
Apache HTTP Server is software that serves web pages and files in response to browser requests. Its release record dated November 11 lists version 2.4.71 as the fix for CVE-2026-119618, a critical vulnerability in its HTTP/2 component, mod_http2. Upstream Apache versions 2.4.55 through 2.4.70 are affected. Red Hat says remote code execution is possible when a vulnerable component is actually receiving HTTP/2 requests. Ubuntu lists fixed packages by operating-system release. NHS England reported a public demonstration of exploitability and assesses exploitation as likely. The reviewed advisories did not confirm attacks in the wild. NHS England alert Apache advisory · Red Hat bulletin · Ubuntu update

1. Which part of the website receives HTTP/2?
When you open a library website, your browser asks for the page, images and fonts. An HTTP/2 connection can carry several requests and replies at once. Apache uses a component called mod_http2 when it handles that traffic. Red Hat says that in a vulnerable module, parts of the server working at the same time can fail to share their temporary workspace safely, corrupting the server’s working data. On a reachable vulnerable server, someone outside the site could run instructions of their choosing with the web server process’s privileges, without logging in. HTTP/2 guide · Affected conditions
| Example setup | Where HTTP/2 arrives | What the team checks |
|---|---|---|
| Apache talks directly to the browser | That Apache server | Whether it loads mod_http2 and serves HTTP/2, and whether its vendor package includes the fix |
| A service in front relays browser requests | The front service receives the browser connection | How it connects to Apache and whether any other route reaches Apache directly |
- Example setup
Apache talks directly to the browser
- Where HTTP/2 arrives
- That Apache server
- What the team checks
- Whether it loads
mod_http2and serves HTTP/2, and whether its vendor package includes the fix
- Example setup
A service in front relays browser requests
- Where HTTP/2 arrives
- The front service receives the browser connection
- What the team checks
- How it connects to Apache and whether any other route reaches Apache directly
The cat asks Q&A
- The researcher
If my browser says HTTP/2, does the Apache server behind it receive HTTP/2 too?
Pocket NotebookA relay can use separate connections to the browser and Apache. Ask the team which protocol Apache itself receives, since the browser only shows its side of the connection.
2. Why 2.4.71 and the Ubuntu package have different numbers
Apache publishes the original release, while an operating-system vendor distributes a package built for its customers. The vendor can bring the fix into an existing version. For example, Ubuntu’s notice for 24.04 LTS lists 2.4.58-1ubuntu8.19 as the fixed apache2 package. Use the complete number, including Ubuntu’s suffix, to compare it with the advisory.
| Stage and owner | Verified status | Evidence to check |
|---|---|---|
| Apache project · fixes and releases the upstream software | Confirmed · upstream 2.4.71 released | Apache advisory |
| Operating-system vendor · supplies the fixed package | Confirmed · Ubuntu 24.04 LTS example is 2.4.58-1ubuntu8.19 | Ubuntu package list · Status by release |
| Operator · applies the fix on running servers | Verify per server | Full package version, application time and records from the instances serving requests |
- Stage and owner
Apache project · fixes and releases the upstream software
- Verified status
- Confirmed · upstream 2.4.71 released
- Evidence to check
- Apache advisory
- Stage and owner
Operating-system vendor · supplies the fixed package
- Verified status
- Confirmed · Ubuntu 24.04 LTS example is
2.4.58-1ubuntu8.19 - Evidence to check
- Ubuntu package list · Status by release
- Stage and owner
Operator · applies the fix on running servers
- Verified status
- Verify per server
- Evidence to check
- Full package version, application time and records from the instances serving requests
The cat asks Q&A
- The researcher
If my server displays 2.4.58, is it still vulnerable?
Pocket NotebookStart with the operating-system release and the full package number. On Ubuntu 24.04 LTS, compare the full number with its advisory and check the operational records to see whether the service is running with that package.
3. What a useful confirmation looks like
Suppose a library runs two servers and its dashboard reports that a package installed successfully. If only one server has started a new process, the other can still handle requests in its old state. Ask the operator for records of both installation and the service that is running. Red Hat describes disabling HTTP/2 while waiting for the fix as a temporary measure. The operator needs to verify the scope and service impact. Red Hat mitigation guidance
Does any Apache server for our service receive HTTP/2? Please share the vendor’s full fixed package version, when it was applied and which serving instances are running it.
The cat asks Q&A
- The researcher
What should I ask if the only reply is that the vendor released a patch?
Pocket NotebookAsk when it was applied and whether it reached every server that handles requests. For a multi-server service, the running version should be verifiable for each server after the update.
To close
Check the servers actually serving traffic
Use Apache’s advisory for the original release and your vendor’s advisory for an operating-system or hosting package. Then check whether the service is running the vendor’s fix on every relevant server.
Sources
- NHS England cyber alertdigital.nhs.uk
- Apache HTTP Server advisoryhttpd.apache.org
- Red Hat security bulletin RHSB-2026-017access.redhat.com
- Ubuntu security notice USN-9090-1ubuntu.com
- Apache HTTP/2 guidehttpd.apache.org
- Ubuntu CVE status by releaseubuntu.com