Apache 2.4.71: check if your server serves HTTP/2
Apache 2.4.71 fixes a critical HTTP/2 flaw. Learn how to check your Apache version, whether HTTP/2 is on, and what to tell your host in a few minutes.
The short answer
Apache HTTP Server 2.4.71, released on 11 November 2026, fixes CVE-2026-119618, a critical flaw in the HTTP/2 module that can lead to remote code execution in versions 2.4.55 through 2.4.70. To see where you stand, check the Apache version, check whether the HTTP/2 module is loaded, read the Protocols setting, and test the site with curl. The fix Apache names is upgrading to 2.4.71, so plan the update even if HTTP/2 looks off.

Reading options
On this page
- What HTTP/2 in Apache actually is
- What Apache's advisory says
- Before you start
- Check your server, step by step
- What to do with what you found
- Variants: panels, NGINX in front, and CDNs
- How to check it worked
- Troubleshooting
- When to ask your host or a developer
- The one message worth forwarding
- Reader questions
- Sources & further reading
Before you start
You need administrator access, a verified private configuration backup copied off the server, and a maintenance window. Use vendor packages or panel-supported updates. Test configuration syntax before any graceful restart; treat the HTTP/1.1-only example as a temporary local measure, not the security fix.
Apache HTTP Server 2.4.71 came out on 11 November 2026 and fixes a critical bug in mod_http2, the part of Apache that speaks HTTP/2. Apache says it affects versions 2.4.55 through 2.4.70 and can lead to remote code execution. You can check your own server in about fifteen minutes: version, module, config, and a curl test.
Here is the detail that caught my eye. Apache's advisory shows the first report reached its security team on 26 October 2026, and the fixed release shipped on 11 November. That is about two weeks from report to patch, which is fast, and it means the fix is out there now, ready for you.
By the end of this guide you will know your Apache version, whether HTTP/2 is loaded and switched on, what your outside test shows, and exactly what to send your host or developer.
What HTTP/2 in Apache actually is
HTTP/2 is a newer way for a browser and a server to talk. HTTP/1.1, the older way, is like a single checkout lane where each item waits its turn. HTTP/2 lets many requests share one connection at the same time, like one cashier scanning several baskets at once.
In Apache, HTTP/2 lives in a module, which is a plug-in piece of the server, called mod_http2. Apache's docs say the module is available from version 2.4.17 and relies on a library called libnghttp2 for the core HTTP/2 engine.
Loading the module is only half the story. Apache's mod_http2 page says you must enable HTTP/2 through the Protocols directive (a config line) before it is used. The core docs say the default is Protocols http/1.1, so out of the box only HTTP/1.1 is allowed.
There are two flavours you will see in config files:
h2means HTTP/2 over TLS, the encrypted connection behind https.h2cmeans HTTP/2 over plain TCP, with no encryption.
Why this matters: when you check your server, you are looking for two things together. Is mod_http2 loaded, and does any Protocols line include h2 or h2c?
What Apache's advisory says
Apache's 2.4 vulnerabilities page lists three CVEs fixed in 2.4.71. A CVE is a public ID number for a security flaw.
- CVE-2026-119618, rated critical: a synchronisation flaw in
mod_http2in the functionassign_headers()that can lead to heap corruption and remote code execution. Affects 2.4.55 through 2.4.70, and standalonemod_h2releases from GitHub, 2.0.8 through 2.0.42. - CVE-2026-106023, rated important: a NULL pointer dereference in
mod_mdthat crashes a child process. Affects 2.4.30 through 2.4.70. - CVE-2026-109163, rated low: a one-byte stack buffer overwrite in
mod_vhost_alias. Affects 2.4.69 and 2.4.70.
"Remote code execution" means someone across the internet could make your server run their code. That is the worst kind of bug for a web server.
Heads up: the advisory does not spell out which configurations can be reached by an attacker, and it does not list a workaround. So I will not tell you "most servers are safe". The honest plan is to check your setup so you know how urgent it is, and to update to 2.4.71 either way.
Before you start
Here is what you need. Nothing in the checking part changes your server, so the risk is low until you edit config.
- SSH access to the server with root or sudo rights, or a host who can run commands for you.
- A computer with
curlinstalled, for the outside test. - Chrome or another browser with developer tools.
- The domain you want to test. I will use
example.comand the IP192.0.2.10as stand-ins. - About 15 minutes for checks, plus a maintenance window if you change config.
- A backup of your Apache config before you edit anything. I show how in Step 3.
Quick tip: if you are on shared hosting, you usually cannot run these server commands. Skip to Step 5 and Step 6, then send your host the message at the end.
Check your server, step by step
Step 1: Find your Apache version
Apache's httpd manual says -v prints the version of httpd and then exits. This command shows the version of the Apache binary on your server.
httpd -vYou should see a line with a version number like 2.4.70 or 2.4.71. If the number is anywhere from 2.4.55 to 2.4.70, you are in the affected range for the critical CVE.
The apachectl manual says it can pass arguments through to the httpd binary. If httpd is not on your path, this does the same job.
apachectl -vHeads up: some Linux distributions rename the binary. If neither command is found, check your distribution's docs or ask your host what the Apache binary is called.
If you want more detail, the manual says -V prints the version and the build parameters. This is handy when you need to send your host the full picture.
httpd -VStep 2: See whether the HTTP/2 module is loaded
The httpd manual says -M dumps a list of loaded static and shared modules. This command filters that list for the HTTP/2 module.
httpd -M 2>/dev/null | grep -i http2If the module is loaded, you will see a line containing http2_module. That name matches the load line in Apache's HTTP/2 guide, which is LoadModule http2_module modules/mod_http2.so.
If the command prints nothing, the module is not loaded in your running config. That is useful to know, but keep reading: you still want to update, because 2.4.71 fixes two other bugs as well.
Quick tip: the manual also says -t with -D DUMP_MODULES prints all loaded modules during a syntax test. This is the same check in another form, useful if -M behaves oddly on your system.
httpd -t -D DUMP_MODULES 2>&1 | grep -i http2Step 3: Find the Protocols setting
First, back up the Apache configuration that actually exists. This unexecuted example creates a private, unique archive for /etc/apache2 or /etc/httpd, verifies that the archive can be listed, and fails visibly instead of hiding errors.
set -eu
umask 077
found=0
for dir in /etc/apache2 /etc/httpd; do
[ -d "$dir" ] || continue
found=1
backup="/root/$(basename "$dir")-config-$(date -u +%Y%m%dT%H%M%SZ)-$$.tar.gz"
tar -C / -czf "$backup" "${dir#/}"
tar -tzf "$backup" >/dev/null
printf 'Verified backup: %s\n' "$backup"
done
[ "$found" -eq 1 ] || { echo 'No common Apache config directory found' >&2; exit 1; }Copy the verified archive to protected off-server storage before editing. It can contain certificate paths and other sensitive configuration, so keep it private. If your panel generates Apache configuration, also use the panel's supported backup or snapshot method.
Now search for every Protocols line. This command looks through both common config locations and prints the file name and line number for each match.
grep -RniE "^\s*Protocols\s" /etc/apache2 /etc/httpd 2>/dev/nullRead each result like this:
- A line such as
Protocols h2 http/1.1allows HTTP/2 over TLS. - A line such as
Protocols h2 h2c http/1.1allows HTTP/2 over TLS and in cleartext. - A line such as
Protocols http/1.1allows only HTTP/1.1. - No
Protocolsline at all means the default, which the core docs give asProtocols http/1.1.
Why this matters: the core docs say a Protocols line in a virtual host replaces the one in the main server config. A virtual host is one website's block in the config. So one site can have HTTP/2 on while the server-wide line says HTTP/1.1. Check every match, not only the first.
Step 4: Check which MPM you run (cPanel servers)
An MPM, or multi-processing module, decides how Apache handles many visitors at once. It matters here because cPanel's HTTP/2 module page says their mod_http2 package is not compatible with mod_mpm_itk, mod_mpm_prefork or mod_ruid2.
cPanel gives this command to see which MPM package you have.
rpm -qa | grep mpmYou will see a package name that includes the MPM, for example one containing mod_mpm_prefork or mod_mpm_event. cPanel also says new cPanel and WHM installs get mod_mpm_prefork by default.
Made-up example: Sana runs a small agency VPS on cPanel. Her rpm output shows mod_mpm_prefork, and Step 2 prints nothing. That tells her HTTP/2 is very likely not loaded, which lowers the urgency a little. She still schedules the EasyApache update for tonight, because the update is the real fix.
On a server without cPanel, the same httpd -M list from Step 2 includes the MPM. Look for a line that starts with mpm_, such as mpm_event_module.
httpd -M 2>/dev/null | grep -i mpmStep 5: Test from outside with curl
Now test what a real client gets. First, Apache's HTTP/2 guide says to check that your curl supports HTTP/2 by looking at its Features line. This command prints curl's version and features.
curl -VLook for HTTP2 in the Features line. If it is missing, your curl cannot test HTTP/2 and the result below will always show 1.1.
The curl manual says that for HTTPS, curl negotiates HTTP/2 in the TLS handshake by default. It also documents -w with the variable http_version, which is the HTTP version that was effectively used. This command fetches your home page, throws away the body, and prints only the version.
curl -s -o /dev/null -w '%{http_version}\n' https://example.com/A result of 2 means curl negotiated HTTP/2; 1.1 means it used HTTP/1.1. This command is an unexecuted example here, so run it from your own network and keep the CDN/origin caveat below in mind.
If you prefer to see the headers, -I fetches the headers only. This command prints the first line of the response, the status line, which shows the HTTP version the server used. The curl manual describes the -I option.
curl -sI https://example.com/ | head -n 1Heads up: if your site sits behind a CDN or a reverse proxy, curl talks to that front layer, not to Apache. The curl manual documents --resolve, which gives curl a custom address for a host and port. This command sends the request straight to your origin IP while keeping the right hostname, so you see what Apache itself answers.
curl -s -o /dev/null -w '%{http_version}\n' --resolve example.com:443:192.0.2.10 https://example.com/Replace 192.0.2.10 with your server's real public IP. If your origin only accepts traffic from the CDN, this test may time out, which is expected.
Step 6: Check in the browser
Open your site in Chrome, open DevTools, and go to the Network tab. Reload the page so DevTools records the requests.
Chrome's docs say you can right-click the header of the Requests table and choose which columns to show. Turn on Protocol. Chrome describes that column as the protocol of the request, for example h2 for HTTP/2 and h3 for HTTP/3.
If you see h3, the browser used HTTP/3, which usually comes from a CDN in front of the server. That is one more reason to use the --resolve test from Step 5 for the origin. I wrote more about that in our guide to enabling HTTP/3 with Cloudflare and checking it with curl.
What to do with what you found
Put your answers side by side:
- Version: is it between 2.4.55 and 2.4.70?
- Module: did Step 2 show
http2_module? - Config: does any
Protocolsline includeh2orh2c? - Outside test: did the origin test print
2?
If the version is in range and the module is loaded with h2 or h2c in Protocols, treat this as urgent and update today. If the version is in range but HTTP/2 looks off, still update soon, because the advisory does not say that only HTTP/2 setups matter, and 2.4.71 also fixes the mod_md and mod_vhost_alias bugs.
Updating on cPanel and WHM
cPanel's EasyApache 4 change log shows version 25.96, dated 12 November 2026, which updates ea-apache24 from 2.4.70 to 2.4.71. The same entry lists CVE-2026-119618 as critical and CVE-2026-109163 as low.
I did not verify cPanel's exact update steps today, so I will not guess them. Check cPanel's own documentation for updating EasyApache 4 packages, or ask your host to apply EasyApache 4 version 25.96. The HTTP/2 module itself is installed or removed in WHM > Home > Software > EasyApache 4, according to cPanel's module page.
Updating outside cPanel
Use the package manager or build process you used to install Apache, and confirm the result with httpd -v afterwards. If your Apache comes from a Linux distribution's package, check that distribution's own security notice for CVE-2026-119618 to see which package version carries the fix.
If you cannot update today
Apache does not list a workaround, so anything here is a stopgap, and you should talk to your host first. The documented behaviour is this: the mod_http2 page says when a server or virtual host does not have h2 or h2c in Protocols, the connection is never inspected for an HTTP/2 preamble.
If your change process allows it, a temporary exposure-reduction step is to allow HTTP/1.1 only on the affected virtual host. Apache does not list this as a workaround, and it is not a substitute for 2.4.71 or a vendor backport. Test on staging, record every original Protocols line, expect HTTP/2 performance to disappear, and use the following only as a reviewed local change.
Protocols http/1.1Before you restart, test the config. The apachectl manual says configtest parses the config files and reports Syntax Ok or the exact error.
apachectl configtestIf you see Syntax Ok, apply the change with a graceful restart, which the manual says does not abort open connections and checks the config first.
apachectl gracefulRollback: restore each recorded Protocols line from the verified backup, run apachectl configtest, then use apachectl graceful only after Syntax Ok. On cPanel servers, hand edits to generated Apache files can be overwritten. I did not verify a supported cPanel Protocols override today; use EasyApache 4 or ask the host rather than editing generated files.
Variants: panels, NGINX in front, and CDNs
cPanel's module page says HTTP/2 through mod_http2 only works when Apache is reached directly. If your cPanel server uses NGINX in front, cPanel points to a separate ea-nginx-http2 package for that. In that setup, the HTTP/2 a browser sees may come from NGINX, so the curl test alone cannot tell you whether Apache's module is in use. Steps 1 to 3 on the server are what count.
The same logic applies to Cloudflare or any CDN. The browser talks HTTP/2 or HTTP/3 to the CDN, and the CDN talks to your origin however it is set up. Use the --resolve test against the origin IP.
I did not verify Plesk or DirectAdmin steps today. If you use one of those panels, check its official docs for how it ships Apache updates, or ask your host which Apache version is running.
Why this matters: on many panels, Apache sits behind something else. Your outside test tells you what visitors get. Your server checks tell you what Apache is doing. You need both.
How to check it worked
After the update, run these again and compare.
httpd -vshould now show 2.4.71 or a distribution package your vendor marks as fixed for CVE-2026-119618.httpd -M 2>/dev/null | grep -i http2showshttp2_moduleonly if you meant to keep HTTP/2.curl -s -o /dev/null -w '%{http_version}\n' https://example.com/prints2if HTTP/2 is still on, or1.1if you turned it off.- In Chrome DevTools, the Protocol column shows
h2for HTTP/2 requests to your own domain, if HTTP/2 is on. - On cPanel, ask your host to confirm that EasyApache 4 version 25.96 or later is installed, since the change log says it updates
ea-apache24to 2.4.71.
If you switched HTTP/2 off as a stopgap, put it back once the update is in place, then rerun the curl test to confirm you see 2 again. While you have the config open, it is a good time to check your TLS settings too, since HTTP/2 over TLS has its own rules. Our guide on checking and enabling TLS 1.3 on Apache, Nginx and WHM covers that.
Troubleshooting
curl always prints 1.1, even though Protocols has h2
Likely cause: your curl was built without HTTP/2. Fix: run curl -V and look for HTTP2 in the Features line. If it is missing, test from another machine or a newer curl.
The browser falls back to HTTP/1.1 on an h2 site
Likely cause: the TLS setup. Apache's HTTP/2 guide says a browser that meets an h2 server with an unsuitable cipher suite refuses HTTP/2 and falls back to HTTP 1.1. The mod_http2 page says H2ModernTLSOnly is on by default and requires at least TLSv1.2 and none of the ciphers on the RFC 7540 Appendix A list. Fix: review your mod_ssl cipher settings and make sure TLS 1.2 or newer is allowed.
Visitors get "421 Misdirected Request"
Likely cause: several virtual hosts share one certificate but have different SSL settings. The mod_http2 page says Apache detects this and returns 421 Misdirected Request. Fix: give those virtual hosts exactly the same protocol, cipher and client verification settings.
HTTP/2 works in curl over http:// but never in the browser
Likely cause: that is cleartext HTTP/2, h2c. Apache's HTTP/2 guide says most browsers speak HTTP/2 only on https: URLs, and it names curl as a client that supports h2c. Fix: test the https:// address, which uses h2, and make sure the site has a valid certificate.
Apache will not restart after you edit Protocols
Likely cause: a typo or a line in the wrong place. Fix: run apachectl configtest, which the manual says reports the exact syntax error, then correct the line or restore your backup from Step 3.
Protocols h2 is set, but the site still speaks HTTP/1.1
Likely cause: the module is not loaded, or a virtual host has its own Protocols line that replaces the server-wide one. Fix: run the Step 2 check and look at every match from the Step 3 search. If you run prefork, note that Apache's HTTP/2 guide says prefork has severe restrictions with HTTP/2, and cPanel says its module is not compatible with mod_mpm_prefork.
The --resolve test hangs or times out
Likely cause: a firewall only lets the CDN reach your origin. Fix: run the test from the server itself using its public IP, or ask your host to run it for you.
When to ask your host or a developer
Ask for help if you are on shared hosting, if you cannot run httpd -v, or if you are not sure which config file your panel uses. Also ask if your Apache came from a vendor build that does not match the version numbers here, since the fix may be backported under a different number.
Security note: once this is patched, it is worth a quick look at your response headers as well. Our post on checking security headers on Apache and Nginx walks through it with curl.
The one message worth forwarding
Copy this to your host, developer or whoever runs your server:
"Hi, Apache released 2.4.71 on 11 November 2026 to fix CVE-2026-119618, a critical bug in the HTTP/2 module that affects 2.4.55 through 2.4.70 (see the Apache 2.4 vulnerabilities page on httpd.apache.org). Can you please tell me the Apache version on my server, whether the HTTP/2 module is loaded, and what the Protocols lines say, and apply the 2.4.71 update or your vendor's fixed package? On cPanel this is EasyApache 4 version 25.96 from 12 November 2026. Thanks."
Check the version, check the module, check Protocols, then update to 2.4.71 whatever you find.
Reader questions
Which Apache versions are affected by CVE-2026-119618?
Apache lists Apache HTTP Server 2.4.55 through 2.4.70 as affected. It also lists the standalone HTTP/2 module releases from GitHub, versions 2.0.8 through 2.0.42.
If my site loads over HTTP/1.1 in curl, am I safe?
It is a good sign, but it is not proof. A CDN or a proxy in front can hide what the origin server does, and the advisory does not describe which setups are reachable, so update to 2.4.71 anyway.
Does turning off HTTP/2 fix the flaw?
Apache does not list a workaround in its advisory. The fix it names is the 2.4.71 release, so treat any change to HTTP/2 settings as a short stopgap and still update.
My server uses cPanel. Is there a fixed package?
Yes. cPanel's EasyApache 4 change log shows version 25.96, dated 12 November 2026, updating the ea-apache24 package from 2.4.70 to 2.4.71 and listing CVE-2026-119618 as critical.
Does HTTP/2 use more server memory?
cPanel's documentation for its HTTP/2 module says HTTP/2 is resource intensive and can increase your server's memory usage. Keep an eye on memory after you turn it on or update.
Do browsers use HTTP/2 over plain http:// links?
Apache's HTTP/2 guide says most browsers speak HTTP/2 only on https: URLs. Cleartext HTTP/2, called h2c, is mainly used by non-browser clients such as curl.
Was this guide helpful?
Help us make the next update better.
Sources & further reading
- Apache httpd 2.4 vulnerabilities (Fixed in 2.4.71)
- Apache HTTP/2 module documentation
- Apache HTTP/2 guide
- Apache core documentation, Protocols directive
- Apache httpd program manual
- Apache apachectl manual
- cPanel EasyApache 4 change log
- cPanel Apache module: HTTP2
- curl man page
- Chrome DevTools Network features reference
What changed
Verified Apache 2.4.71 and CVE-2026-119618 against the Apache security page. Replaced a collision-prone, error-suppressing backup command with a private unique verified archive; removed an unverifiable first-person test claim; clarified that HTTP/1.1-only is an unexecuted local exposure reduction, not an Apache workaround; added rollback and original media.
Originally published . About our editorial updates.



