php2shell patches (CVE-2026-109618 and CVE-2026-109619) for EOL PHP are out now. With sales replies slower than usual due to high demand, the fastest route to patched packages is to buy ELS for Runtimes online (opens in new tab). Read the patch FAQ

Go straight to an AI summary of this blog post instead

  • Summarize this post with Perplexity
  • Summarize this post with Gemini

TuxCare Status Update for November 16, 2026

TuxCare has released Endless Lifecycle Support fixes for CVE-2026-119618 on Ubuntu 20.04, Debian 10 and 11, Amazon Linux 2, and Alpine Linux 3.18, along with fixes for TuxCare 9.6 ESU and TuxCare 9.8 ESU. Ubuntu 16.04, Ubuntu 18.04, CentOS 7, and AlmaLinux 9.2 ESU aren’t affected and need no action for this CVE.

Get Endless Lifecycle Support →

Key Takeaways

  • A race in Apache’s mod_http2 corrupts heap memory, and Apache warns it can lead to remote code execution.
  • Only servers that load mod_http2 and offer HTTP/2 through the Protocols directive are exposed to this bug.
  • Version numbers can mislead here because Ubuntu 20.04 and 22.04 are affected despite sitting below the upstream range.
  • TuxCare’s fixes are out, and Ubuntu 16.04, 18.04, CentOS 7, and AlmaLinux 9.2 ESU are unaffected.

Apache shipped httpd 2.4.71 on November 11 to close CVE-2026-119618, a bug in mod_http2 that the project rates critical. The flaw sits in a function called assign_headers(), and when the timing lines up, it corrupts heap memory inside an httpd child process. Apache’s advisory says plainly that the flaw can lead to remote code execution. The project hasn’t rated an httpd bug critical since the path traversal flaws fixed in 2.4.50 and 2.4.51 back in 2021.

The attack surface is narrower than the headlines make it sound, since HTTP/2 has to be switched on. Trouble is, plenty of servers have it switched on, and nobody remembers who did it. And the usual shortcut of comparing a version string against the advisory gives the wrong answer on some very popular distros.

So it’s worth spending ten minutes on this one. The sections below walk through how the bug works, how to tell quickly whether a server is exposed, what to do if a fix can’t go in today, and where things stand for teams running older releases under TuxCare’s Endless Lifecycle Support.

What Actually Breaks Inside mod_http2

HTTP/2 lets a client multiplex many streams over a single connection. Apache’s mod_http2 hands those streams to worker threads so they can be processed concurrently, and that concurrency is where this bug lives.

According to the public write-up that accompanies a proof of concept on GitHub, assign_headers() writes a synthesized Content-Length: 0 header into memory tied to the connection’s allocator while another thread can be using that same allocator. Red Hat describes the root cause the same way, as a worker thread writing into memory owned by the connection through a shared, lock-free allocator. Nothing keeps the two threads out of each other’s way, which makes this a textbook CWE-362 race, and the result is a corrupted heap in the child process.

Red Hat’s notes add a useful detail. The mod_http2 builds in RHEL 9 and 10 give each HTTP/2 stream a separate allocator, which makes the race much harder to exploit, so Red Hat rates those products Important rather than Critical. Builds where stream memory comes out of the connection’s allocator are the ones to worry about most.

No credentials are needed for any of this. An attacker only has to reach the server over HTTP/2, either h2 over TLS or cleartext h2c.

Who Is Actually Exposed

Three things have to be true at the same time. The installed mod_http2 code has to fall in the vulnerable range, the module has to be loaded, and a Protocols directive somewhere in the config has to offer h2 or h2c. Take away any one of those, and this CVE doesn’t apply.

The first condition is where people get caught. Upstream lists httpd 2.4.55 through 2.4.70 and the standalone mod_h2 module from 2.0.8 through 2.0.42. Plenty of admins will read that, run apache2 -v, see 2.4.41 on Ubuntu 20.04 or 2.4.52 on Ubuntu 22.04, and move on. That would be a mistake. Canonical backported newer mod_http2 code into its stable releases, so both Ubuntu releases are affected, and both have fixes. Ubuntu’s own CVE tracker spells this out.

RHEL-family systems set a similar trap. Red Hat ships mod_http2 as a separate package, so the httpd version number tells you very little there. Check the mod_http2 package itself. Red Hat says builds older than 2.0.8 don’t contain the affected code, which is why RHEL 8 and earlier are out of scope.

The advisory’s version range describes upstream source releases, not necessarily what your distro packaged. To know where a server really stands, compare the installed package against the fixed version in the vendor’s security advisory. The package changelog makes a good second check.

How Serious Is It Really

That depends on who you ask, and the disagreement is wider than usual.

Apache calls it critical without publishing a CVSS score. Red Hat scores it 9.8 with low attack complexity. The CVE record at CVE.org and Ubuntu’s tracker both list 8.1 with high attack complexity, a nod to the fact that winning a race between threads rarely happens on the first try.

Both numbers hold up. A race that needs many attempts is harder to land than a plain overflow. But attackers can automate attempts against an internet-facing web server, and Apache typically replaces crashed child processes, which leaves room for more tries. All those crashes can degrade the service along the way, too.

No attacks have been publicly reported as of November 16. The CVE isn’t in CISA’s Known Exploited Vulnerabilities catalog, and CISA’s assessment on the CVE record lists exploitation as none. A proof of concept on GitHub does reproduce the heap corruption in a lab, though, and Red Hat states that public research has demonstrated a reliable exploit against a default-configured server with mod_http2 enabled. Red Hat doesn’t identify the research behind that claim. Its advisory also specifies that only servers offering h2 or h2c through the Protocols directive are vulnerable. On any internet-facing server with HTTP/2 enabled, this belongs at the top of this week’s patch list.

Apache 2.4.71 also fixes two smaller issues, CVE-2026-106023 (a mod_md NULL pointer dereference rated important) and CVE-2026-109163 (a low-severity mod_vhost_alias overflow). One of the researchers credited on that second fix works at TuxCare. Upgrading to upstream 2.4.71 fixes all three. Distro packages may backport only some of those fixes, so check the vendor advisory to see what’s included.

Where the Major Distros Stand

Fix status as of November 16, 2026, based on each vendor’s public advisory.

Distribution Fixed package Notes
Upstream Apache httpd 2.4.71 Released November 11
RHEL 10 (current minor release) mod_http2-2.0.29-5.el10_3.1 RHSA-2026:98978, rated Important
RHEL 9 (current minor release) mod_http2-2.0.26-7.el9_9.1 RHSA-2026:98981, rated Important
RHEL 8 and earlier Not affected Ships mod_http2 older than 2.0.8
Ubuntu 26.10 apache2 2.4.68-1ubuntu6.2 USN-9090-1
Ubuntu 26.04 apache2 2.4.66-2ubuntu2.8 USN-9090-1
Ubuntu 24.04 apache2 2.4.58-1ubuntu8.19 USN-9090-1
Ubuntu 22.04 apache2 2.4.52-1ubuntu4.27 Affected despite the older version number
Ubuntu 20.04 apache2 2.4.41-4ubuntu3.23+esm11 Through Ubuntu Pro
Ubuntu 18.04 and 16.04 Not affected Predates the vulnerable code
Debian 13 apache2 2.4.71-1~deb13u1 DSA-6620-1
Debian 12 apache2 2.4.71-1~deb12u1 DLA-4902-1

Red Hat also shipped separate fixes on November 11 for RHEL 9.6, 9.8, 10.0, and 10.2 Extended Update Support and for RHEL 9.4 Update Services for SAP Solutions. Systems pinned to one of those releases should take the build from the matching advisory.

Check a Server in About Two Minutes

Start with whether HTTP/2 is even in play. The apachectl command works on both distro families, since Debian and Ubuntu ship it as a link to apache2ctl.

sudo apachectl -M | grep -w http2_module

If the command runs cleanly and http2_module doesn’t show up, the module isn’t loaded, and this CVE doesn’t affect the server. If the command throws an error, sort that out first. A blank result from a command that failed proves nothing.

If the module is loaded, look at which protocols the config offers. On Debian and Ubuntu, the config lives under /etc/apache2/.

sudo grep -RinE '^[[:space:]]*Protocols[[:space:]]' /etc/apache2/

On RHEL-family systems, search /etc/httpd/ instead.

sudo grep -RinE '^[[:space:]]*Protocols[[:space:]]' /etc/httpd/

Some setups pull in config from other directories, and what counts is the active virtual host rather than a line sitting somewhere on disk. A Protocols directive inside a virtual host overrides the global setting, so confirm from the outside as well.

curl -sSI --http2 -o /dev/null -w '%{http_version}\n' https://your-server/

A result of 2 means the endpoint curl reached negotiated HTTP/2, and 1.1 means it didn’t. If a CDN or reverse proxy sits in front, that endpoint may not be Apache at all, so check the origin separately. The test needs a curl build with HTTP/2 support, and it’s worth running against each virtual host that matters. It also only covers HTTPS. For a cleartext h2c endpoint, point curl at an http:// URL and run it twice, once with --http2 to test the HTTP/1.1 Upgrade path and once with --http2-prior-knowledge to test a direct HTTP/2 connection. Those are separate negotiation paths, so a failure on one doesn’t rule out the other.

Next, find out whether the installed package already carries the fix. On RHEL-family systems, including TuxCare ESU, check the mod_http2 changelog.

rpm -q --changelog mod_http2 | grep CVE-2026-119618

On Amazon Linux 2, the fix ships in the httpd package, so check that changelog instead.

rpm -q --changelog httpd | grep CVE-2026-119618

On Debian and Ubuntu, the changelog ships with the package.

zgrep CVE-2026-119618 /usr/share/doc/apache2/changelog.Debian.gz

A changelog entry that names the CVE is good confirmation. A blank result doesn’t prove much either way, though, since vendors word their changelogs differently and custom builds may not carry the same notes. The deciding check is the installed package version against the fixed version in the vendor’s advisory. These commands pull that version on each platform.

Platform Command
Debian and Ubuntu dpkg-query -W -f='${Version}\n' apache2
RHEL-family systems and TuxCare ESU rpm -q mod_http2
Amazon Linux 2 rpm -q httpd
Alpine Linux apk list --installed apache2

Containers deserve their own look because an image built in September won’t pick up a fix installed on the host.

If Patching Has to Wait

The mitigation is blunt, but it works. Red Hat confirms that servers serving only HTTP/1.1 aren’t vulnerable.

The cleanest option is to disable the module. On Debian and Ubuntu, the chain below only restarts Apache if the config test passes.

sudo a2dismod http2 && sudo apache2ctl configtest && sudo systemctl restart apache2

On RHEL-family systems, comment out the LoadModule http2_module line (usually in /etc/httpd/conf.modules.d/10-h2.conf), run apachectl configtest, and restart httpd only once it comes back clean.

The other option keeps the module loaded but stops offering HTTP/2 by setting Protocols http/1.1. That only works if every virtual host with its own Protocols line gets the same edit, because a global setting won’t override a vhost that explicitly asks for h2. This is the step people most often get wrong. Whichever route you pick, run the curl check again afterward.

Which way to go? If a CDN or load balancer terminates HTTP/2 and talks to Apache over HTTP/1.1, disabling HTTP/2 at the origin should barely register with clients, so do it now. Check how the intermediary connects to the origin first, though, because some setups run HTTP/2 all the way through. If clients connect directly, make sure nothing depends on HTTP/2, disable it temporarily while a fixed package goes in, and then turn it back on. The only real case for leaving it running is a server that nobody outside a trusted network can reach, and even then the patch belongs on this week’s list.

Where TuxCare Stands

TuxCare has released fixed Apache packages for the affected systems it covers, through Endless Lifecycle Support for distros past their end of life and Extended Security Updates for the TuxCare ESU releases. Install the update with the system’s usual package manager, and then restart Apache. The repositories and tooling stay the same.

Product Package Status
Ubuntu 20.04 ELS apache2 Fixed in 2.4.41-4ubuntu3.23+tuxcare.els17
Debian 10 ELS apache2 Fixed in 2.4.59-1~deb10u1+tuxcare.els16
Debian 11 ELS apache2 Fixed in 2.4.67-1~deb11u3+tuxcare.els2
Amazon Linux 2 ELS httpd Fixed in 2.4.69-1.amzn2.0.3.tuxcare.els2
Alpine Linux 3.18 ELS apache2 Fixed in 2.4.62.tuxcare.els16-r0
TuxCare 9.6 ESU mod_http2 Fixed in 2.0.26-4.el9_6.1.tuxcare.els6
TuxCare 9.8 ESU mod_http2 Fixed in 2.0.26-6.el9_8.2.tuxcare.els1
Ubuntu 16.04 ELS apache2 2.4.18 Not affected
Ubuntu 18.04 ELS apache2 2.4.29 Not affected
CentOS 7 ELS httpd 2.4.6 Not affected
AlmaLinux 9.2 ESU mod_http2 Not affected

On TuxCare 9.6 and 9.8 ESU, the fix ships in the mod_http2 package, and httpd itself needs no update. Live status for every product is on the TuxCare CVE tracker.

Running Apache on a distro that’s past its end of life? Endless Lifecycle Support keeps it patched for as long as you need it, with the same package manager and no forced migration.

Why This Won’t Be the Last One

Anthropic’s OSS Scanner, an AI system that looks for vulnerabilities in open source projects, reported this bug to Apache on October 26. Google Cloud Vulnerability Research found it independently a week later. It’s also at least the fifth mod_http2 CVE Apache has fixed this year, after a double free with possible RCE that was fixed in 2.4.67 and a run of memory corruption and denial of service bugs fixed in 2.4.68 and 2.4.69.

Apache’s October release alone fixed 20 CVEs, and several were credited to AI-assisted research teams. Automated research keeps finding bugs in mature, heavily reviewed code, and each one adds to the patching workload for teams already juggling a long list of open source components. When a package an application depends on has reached end of life upstream, there’s no guarantee anyone will still ship fixes for the versions in use.

The same lifecycle problem reaches past web servers into the application dependencies developers install every day, and that’s the part SecureChain covers. It currently supports JavaScript, Python, Java, Go, and PHP packages, with every package rebuilt from source, malware-scanned, and patched under SLA, including versions that upstream no longer supports. Developers point their package manager or repository manager at it and keep working the way they already do.

See how SecureChain keeps open source dependencies patched for as long as they’re in your stack.

Timeline

Date Event
October 26, 2026 Anthropic’s OSS Scanner reports the flaw to the Apache security team
November 3, 2026 Google Cloud Vulnerability Research reports it independently
November 11, 2026 Apache releases httpd 2.4.71 and publishes the advisory, and Red Hat ships fixed mod_http2 packages for RHEL 9 and 10
November 12, 2026 Ubuntu publishes USN-9090-1, and Debian ships fixed apache2 packages for Debian 12 and 13
November 13, 2026 CISA adds its assessment to the CVE record and finds no known exploitation

Sources

Apache HTTP Server 2.4 vulnerabilities

CVE-2026-119618 record at CVE.org

Red Hat CVE-2026-119618

Ubuntu CVE tracker for CVE-2026-119618

Debian security tracker for CVE-2026-119618

oss-security announcement

Public proof of concept and technical write-up on GitHub

TuxCare CVE tracker

Join 4,500+ Linux & Open Source Professionals!

2x a month. No spam.

Table of Contents
Get the open-source security answers you need

Join 4,500+ Linux & Open Source Professionals!

2x a month. No spam.