NewsWebsite creationApache HTTP Server 2.4.71

Apache HTTP Server 2.4.71: check your site behind Cloudflare

Apache fixes a critical HTTP/2 vulnerability. Here are the affected versions and the checks to run, even behind Cloudflare.

Mehdi B.

Co-founder · SEO & digital strategy

Apache HTTP Server 2.4.71: check your site behind Cloudflare
In brief

Apache HTTP Server 2.4.71 fixes a critical flaw in the handling of HTTP/2 connections. Check the origin server configuration, even behind Cloudflare, then install the fixed version or the security package provided by your distribution.

On 11 November 2026, Apache HTTP Server 2.4.71 fixes a critical flaw that allows remote code execution. It affects the server that hosts your website, even when Cloudflare sits in front of it. We recommend dealing with exposed installations without delay, and checking that their HTTP/2 connection actually works as expected.

Apache HTTP Server 2.4.71: what does this version fix?

The vulnerability CVE-2026-119618 affects mod_http2, the module that lets Apache communicate over HTTP/2. This protocol handles several requests at once on a single connection. A coordination defect between these operations can corrupt the server’s memory and allow an attacker to run commands on it.

Apache versions 2.4.55 to 2.4.70 are affected. Exploitation does not require a user account, but assumes the attacker can send HTTP/2 requests to the vulnerable server. An installation that only serves HTTP/1.1 connections is not exposed to this flaw.

Apache classes this vulnerability as critical and credits its discovery to Google Cloud researchers and an Anthropic tool. For your business, the deciding factor remains the installed configuration. The presence of Apache software is not, on its own, enough to conclude that your site is vulnerable.

Does Cloudflare also protect the server that hosts your site?

Apache HTTP Server 2.4.71: check your site behind Cloudflare

Take an online shop whose visitors go through Cloudflare. Two separate connections are involved: the one from the browser to Cloudflare, then the one from Cloudflare to the origin server. The origin server is the machine that runs the application and serves its content.

According to its documentation, Cloudflare can communicate with this machine over HTTP/2 thanks to the “HTTP/2 to Origin” setting. Seeing Cloudflare in the domain configuration therefore does not prove that Apache receives only HTTP/1.1. You need to examine the connection behind the service, not just the one visible in the browser.

Another check: does the server accept direct connections that bypass Cloudflare? If a reachable address leads to Apache with HTTP/2 enabled, that path must be examined too. The same reasoning applies when an Nginx server receives visits before passing them on to Apache.

For our fictional shop, a compromise could affect the information accessible to the Apache process or interrupt the service. The risk goes beyond an unavailable page: it also concerns the operations that depend on the site. Prepare the list of functions to check after the intervention: customer login, basket and validation of a test order.

Which fix should you apply without disrupting your site?

The version published by Apache that fixes this flaw is 2.4.71. On a managed hosting setup using a Linux distribution’s packages, apply the fix provided by that distribution. A fix can be backported, that is, built into an older version without taking the number of the latest Apache version.

Ask for a security advisory reference that explicitly mentions this CVE and the installed package. This evidence avoids mistaking an old version number for a lack of protection. Also prepare a usable backup and an intervention window suited to the shop’s activity.

If the update has to wait, a temporary measure is to disable HTTP/2 on Apache, then restart the service. The technical team then removes the values h2 and h2c of the directive Protocols to keep http/1.1. This change must be checked on the server concerned before the measure is considered effective.

What evidence should you ask your technical team for?

  1. Which server actually responds? Have the origin machine, the intermediaries and any direct access recorded. Match each Apache instance to its version and its patch status.

  2. Is HTTP/2 active on Apache? Ask for confirmation of the loading of mod_http2 and authorised protocols. A result obtained only on the public address behind Cloudflare does not answer that question.

  3. Does the fix work in production? Keep the reference of the patched package, the confirmation of the required restart and the results of the shop tests. This post-intervention check matches the one described in our news item on Debian fixes and the check after restart.

Sources

SecurityApacheHostingCloudflare
Mehdi B.
About the authorMehdi B.

Co-founder of Smart Impact. Hooked on the web from the start, he launched his first project in 2006: an online music magazine still running today. With close to 20 years of SEO experience, a Swiss federal diploma in marketing and a solid geek streak, he turns clients' ideas, sometimes hazy ones, into concrete digital projects with his team.

LinkedIn
Further reading