On this page
- What happened?
- Who found it, and how fast was it fixed?
- Am I affected?
- How bad is it?
- What should I do now?
- What do the Linux distributions say?
- What we don't know yet
- My take
- Frequently asked questions
- What is CVE-2026-119618?
- Which Apache versions are affected?
- How do I fix the Apache HTTP/2 vulnerability?
- Is CVE-2026-119618 being exploited?
- Does the Apache flaw affect my website host?
- Sources
Quick answer. Apache HTTP Server 2.4.55 to 2.4.70 has a critical flaw in its HTTP/2 module that can let an attacker run code on servers with HTTP/2 enabled. Update to 2.4.71 and restart Apache, or turn HTTP/2 off until you can.
What happened?
On November 11, the Apache project shipped HTTP Server 2.4.71 and disclosed three security fixes in it, one rated critical, one important and one low, according to Apache's own advisory page. The critical one is CVE-2026-119618, a bug in mod_http2, the module that gives Apache its HTTP/2 support. The project says it can lead to remote code execution, which means someone on the internet could run commands on your web server.
It affects Apache versions 2.4.55 through 2.4.70, plus the separate mod_h2 module from GitHub in versions 2.0.8 through 2.0.42. The announcement to the oss-security mailing list came from the Apache project the same day.
Who found it, and how fast was it fixed?
Apache credits two finders. One is Anthropic's open source scanner, which reported the bug on October 26. The other is Anthony Weems and Simon Scannell of Google Cloud's vulnerability research team, who reported it on November 3. The fix landed and the release went out on November 11, per Apache's page. Panelica's write-up points out that two teams reaching the same bug within about a week suggests that code path was ripe for anyone fuzzing HTTP/2.
Am I affected?
Not every Apache server is. Several sources agree the flaw matters only when HTTP/2 is actually in use. HelixML notes that upstream Apache's default setting is plain HTTP/1.1, so a server needs to have switched on h2 or h2c through the Protocols directive. Panelica adds that checking the version number is not enough: you also need to know whether the module is loaded at all.
Your server is probably exposed if all of these are true:
- It runs Apache HTTP Server between 2.4.55 and 2.4.70.
- The mod_http2 module is loaded.
- HTTP/2 is enabled for at least one site.
How bad is it?
Red Hat scores it 9.8 out of 10, and that is a vendor score. HelixML adds that Red Hat rates the RHEL 9 and 10 builds as Important. Panelica stresses that the National Vulnerability Database had not published its own score yet, so be wary of anyone saying NVD gave it a 9.8.
Wiz, a cloud security company, says 64% of the cloud environments it sees contain resources running a vulnerable version, and 51% have publicly exposed instances. Wiz adds that these figures do not take configuration into account, so they say how many servers run a vulnerable version, not how many can be attacked. This is a vendor's own data, and I'd read it as a sign of how common Apache is, not as a count of hacked servers.
As of November 12, the sources report no attacks in the wild. Wiz said at publication that no exploit was available. The sources disagree on how close an attack is. HelixML says the public reproduction labs show memory corruption and not a working code-execution attack, but it also quotes Red Hat saying public research has demonstrated a reliable exploit against a default-configured server. The flaw was not on the CISA known exploited list when HelixML wrote. With the sources split on that point, I wouldn't wait.
What should I do now?
- Update to Apache 2.4.71 or later. The fix ships inside httpd 2.4.71. HelixML says there is no fixed standalone mod_h2 release, so if you run that separate module, the safe route is the bundled one in 2.4.71. Wiz's table lists a different standalone fix, which HelixML calls wrong.
- Restart Apache. CloudLinux warns that Apache keeps running the old module until it restarts, so an installed update does nothing until then.
- If you cannot patch today, turn HTTP/2 off. Wiz suggests setting the Protocols directive to http/1.1 only, which removes the attack path.
- Confirm the fix landed. On CloudLinux 9 and 10 the fixed mod_http2 builds keep their older module numbers, so CloudLinux suggests searching the package changelog for the CVE number.
If you do not run servers yourself, you can still act. Ask your web host whether they are on 2.4.71 or have turned HTTP/2 off, and ask when.
What do the Linux distributions say?
Fixes are arriving at different speeds. HelixML reports that on November 12 Debian had fixed only its unstable branch, while bookworm, trixie and forky were still vulnerable. CloudLinux 9 and 10 are affected and have fixed builds. The system Apache on CloudLinux 7 and 8 is not affected, because version 7 has no HTTP/2 module and version 8's predates the vulnerable code. The EasyApache 4 Apache that CloudLinux rebuilds for cPanel servers still needs the 2.4.71 update, and that build is in the stable channel. On Ubuntu 22.04, CloudLinux says Ubuntu had not released a fix yet, though the module is off by default there.
What we don't know yet
Three things are still open. NVD has not issued its own severity score. Nobody outside the project has confirmed exploitation in the wild, and the lack of reports is not proof of safety. And the cloud exposure figures come from one vendor and ignore how each server is set up.
The sources here are Apache's own record plus security and hosting sites.
My take
For a small business the practical question is not how clever the bug is. It is whether someone is responsible for your server and has read this advisory. If that someone is a hosting company, I'd send a short email today. If it is you, I'd patch and restart before the weekend, and turn off HTTP/2 in the meantime if a restart is risky. A critical flaw with a public reproduction lab and a patch that already exists is the easy kind of problem to fix and the expensive kind to ignore.
Frequently asked questions
What is CVE-2026-119618?
It is a critical flaw in mod_http2, the HTTP/2 module of Apache HTTP Server, that can corrupt memory and let an attacker run code on the server without logging in. It affects Apache 2.4.55 through 2.4.70 and was fixed in version 2.4.71 on November 11, 2026.
Which Apache versions are affected?
Apache HTTP Server 2.4.55 through 2.4.70 is affected, along with the separate mod_h2 module from GitHub in versions 2.0.8 through 2.0.42. Only servers that load mod_http2 and have HTTP/2 enabled are exposed. The fix is in Apache 2.4.71, so anything older needs an update.
How do I fix the Apache HTTP/2 vulnerability?
Update to Apache 2.4.71 or later and restart Apache, since the old module keeps running until a restart. If you cannot patch yet, switch HTTP/2 off by limiting the Protocols directive to http/1.1. Check the fixed version with your host or distribution.
Is CVE-2026-119618 being exploited?
No attacks in the wild had been reported when Wiz and HelixML wrote about it, and no exploit was said to be available at Wiz publication. A public reproduction lab exists, however, so patching quickly is wise. Absence of reports does not prove servers are safe.
Does the Apache flaw affect my website host?
Possibly. Many hosts run Apache, but only those using HTTP/2 on affected builds are exposed, and a fixed distribution package can carry an older module number. Ask your host whether they have moved to 2.4.71 or turned HTTP/2 off.
Sources
- Apache HTTP Server 2.4 vulnerabilities, httpd.apache.org
- oss-security - CVE-2026-119618: Apache HTTP Server: mod_http2: heap corruption and RCE in assign_headers, openwall.com
- Critical RCE Vulnerability in Apache HTTP Server: Everything You Need To Know, wiz.io
- CVE-2026-119618: Apache HTTP/2 RCE Fixed in 2.4.71, helix.ml
- CVE-2026-119618 Apache mod_http2 RCE Analysis, threatlandscape.io
- Apache mod_http2 RCE (CVE-2026-119618): Is Your Server Affected? - Security, panelica.com
- Critical Apache mod_http2 flaw CVE-2026-119618, cloudlinux.com
- Apache HTTP Server 2.4.71 Releases Critical HTTP/2 RCE Fix for Widespread Vulnerabilities, linuxcompatible.org
Tech news, checked twice, in your inbox.
One calm email when a story is worth your time. Unsubscribe in one click.



