Apache HTTP Server 2.4.71: Patch mod_http2 CVE-2026-119618

11/20/2026
6 min read
Apache HTTP Server 2.4.71 security update graphic: orange shield with a keyhole and the mod_http2 fix CVE-2026-119618

Introduction

Apache HTTP Server 2.4.71, released on November 11, 2026, fixes three vulnerabilities, including CVE-2026-119618, a critical flaw in mod_http2 that the Apache project says can lead to remote code execution. Apache httpd still powers many WordPress, PHP and shared hosting servers, and HTTP/2 is common on modern sites. If you run Apache 2.4.55 or later with HTTP/2, plan the update now.

This article summarizes the official Apache advisory and Linux distribution notices, shows how to check your server, and explains how to update. It contains no exploit details.

Key Facts: Apache HTTP Server 2.4.71 at a Glance

  • What: Apache HTTP Server 2.4.71 (November 11, 2026) fixes CVE-2026-119618, CVE-2026-106023 and CVE-2026-109163.
  • Most serious: CVE-2026-119618, a race condition in mod_http2 (assign_headers()) that can lead to remote code execution. The Apache project rates it critical.
  • Affected: Apache httpd 2.4.55 to 2.4.70 with mod_http2, and standalone mod_h2 2.0.8 to 2.0.42. Distribution packages with older version numbers can also be affected.
  • Severity: critical (Apache project). CVSS v3.1 8.1 from CISA’s enrichment in NVD; Ubuntu rates it “High” priority.
  • Exploitation: none reported. CISA’s SSVC entry lists exploitation as “none,” and the CVE is not in the CISA KEV catalog (version 2026.11.18).
  • Action: upgrade to 2.4.71 or your distribution’s patched package, then restart Apache.

What Does Apache HTTP Server 2.4.71 Fix?

Apache HTTP Server 2.4.71 fixes one critical, one important and one low-severity issue, according to the Apache httpd security page.

CVEModuleIssueApache severityCVSS v3.1 (CISA ADP)
CVE-2026-119618mod_http2Race condition in assign_headers(), heap corruption and possible remote code executionCritical8.1
CVE-2026-106023mod_mdNULL pointer dereference that crashes a child processImportant7.5
CVE-2026-109163mod_vhost_aliasOne-byte stack buffer overwrite (after CVE-2026-63292)Low5.9

The Apache project does not publish CVSS scores. The scores above come from CISA’s Authorized Data Publisher entries in NVD. NVD itself had not finished analyzing CVE-2026-106023 and CVE-2026-109163 when we checked.

Which Apache Versions Are Affected?

Upstream Apache httpd 2.4.70 and earlier are affected, but the exact range depends on the CVE and on how your distribution packages mod_http2.

CVEAffected (Apache project)Fixed in
CVE-2026-1196182.4.55 to 2.4.70; mod_h2 2.0.8 to 2.0.422.4.71
CVE-2026-1060232.4.30 to 2.4.702.4.71
CVE-2026-1091632.4.69 to 2.4.702.4.71

NVD’s descriptions give slightly narrower ranges for the two lower-severity CVEs (ending at 2.4.69). We follow the Apache project’s page.

Why can older distribution versions be affected?

Distributions often backport newer mod_http2 code into older httpd packages. Ubuntu’s security notes say exactly this for CVE-2026-119618, and Ubuntu lists its 22.04 package (based on 2.4.52) as affected and fixed. So check your vendor’s tracker, not just the upstream version number.

DistributionFixed package (CVE-2026-119618)
Ubuntu 26.04 LTS2.4.66-2ubuntu2.8
Ubuntu 24.04 LTS2.4.58-1ubuntu8.19
Ubuntu 22.04 LTS2.4.52-1ubuntu4.27
Ubuntu 20.04 LTS2.4.41-4ubuntu3.23+esm11 (Ubuntu Pro)
Debian 13 (trixie)2.4.71-1~deb13u1 (DSA-6620-1)
Debian 12 (bookworm)2.4.71-1~deb12u1 (DLA-4902-1)

Ubuntu lists 18.04 and older as not affected. For Red Hat, AlmaLinux and other platforms, check the vendor pages linked from the NVD record.

What Is the Security Impact?

The worst case is remote code execution through mod_http2, while the other two issues mainly crash Apache child processes.

What can CVE-2026-119618 do?

The Apache advisory describes a concurrency bug: shared resources are used without proper synchronization in mod_http2’s assign_headers() function. This can corrupt heap memory and, according to the advisory, lead to remote code execution. CISA’s vector marks it as network-reachable without authentication but with high attack complexity. That fits a race condition, which is hard but not impossible to win.

What about mod_md and mod_vhost_alias?

CVE-2026-106023 lets a request crash an Apache child process when mod_md, Apache’s built-in ACME certificate module, is in use. CVE-2026-109163 is a one-byte stack overwrite in mod_vhost_alias that affects only 2.4.69 and 2.4.70. Ubuntu’s notice says it could possibly lead to code execution.

How Do I Check Whether Apache HTTP Server 2.4.71 Is Needed?

Check the installed version and package release, then confirm whether mod_http2 is loaded and HTTP/2 is enabled.

How do I check my Apache version?

apache2 -v          # Debian/Ubuntu
httpd -v            # RHEL/AlmaLinux/Fedora
dpkg -l apache2     # full Debian/Ubuntu package version
rpm -q httpd        # full RPM package version

Compare the full package version with the table above or your vendor’s tracker. On managed or shared hosting, ask your provider whether USN-9090-1, DSA-6620-1 or an equivalent fix is installed.

How do I check whether HTTP/2 is enabled?

apache2ctl -M 2>/dev/null | grep -E "http2|md_module|vhost_alias"
grep -rniE "^\s*Protocols" /etc/apache2 /etc/httpd 2>/dev/null

If http2_module is loaded and a Protocols line includes h2 or h2c, treat CVE-2026-119618 as urgent.

How Do I Fix These Apache Vulnerabilities?

Install Apache HTTP Server 2.4.71 or your distribution’s patched package, then restart Apache.

  1. Back up first. Copy your Apache configuration and, for WordPress, follow our guide on how to back up WordPress.
  2. Update the package. On Ubuntu and Debian run sudo apt update && sudo apt install --only-upgrade apache2. On RPM-based systems use sudo dnf upgrade httpd.
  3. Check and restart. Run apachectl configtest, then restart Apache so all child processes use the fixed code.
  4. Check standalone mod_h2. The advisory lists mod_h2 2.0.8 to 2.0.42 as affected; check the mod_h2 project for a fixed release.
  5. Rebuild containers based on httpd or distribution images.

What if I cannot update right away?

The Apache advisory does not list a workaround, so the update is the fix. If your site does not need HTTP/2, removing h2 and h2c from Protocols takes mod_http2 out of the request path. This is our assessment, not vendor guidance, and it does not address CVE-2026-106023 or CVE-2026-109163.

Additional Security Recommendations

Applying Apache HTTP Server 2.4.71 is the main defense. These habits limit the damage from the next web server bug:

FAQ

Is CVE-2026-119618 being exploited?

No exploitation has been reported as of November 20, 2026. CISA’s SSVC entry lists exploitation as “none,” and the CVE is not in the KEV catalog (version 2026.11.18). Public exploit availability is unknown.

Am I affected if I run Apache 2.4.52 on Ubuntu 22.04?

Yes, unless you have package 2.4.52-1ubuntu4.27 or later. Ubuntu backported newer mod_http2 code, so its 2.4.52 package is affected even though upstream 2.4.52 is older than 2.4.55.

Do I need Apache HTTP Server 2.4.71 if HTTP/2 is disabled?

Yes, still update. CVE-2026-119618 needs mod_http2, but the mod_md and mod_vhost_alias fixes also matter, and a later configuration change could enable HTTP/2.

Is nginx affected by these CVEs?

No. These CVEs are specific to Apache httpd modules. Nginx had its own security release on November 18, 2026.

Conclusion

Apache HTTP Server 2.4.71 closes a critical mod_http2 race condition and two smaller bugs. Check your package version against your vendor’s tracker, install Apache HTTP Server 2.4.71 or the patched package, and restart Apache today.

References

All links below returned HTTP 200 when checked on November 20, 2026.

Related Articles

Last Verified: November 20, 2026. Prepared by SafeWebAcademy from the official Apache HTTP Server advisory, NVD records and Linux distribution security notices linked above. This is not an official Apache Software Foundation publication. Security details can change, so check the linked advisories for updates.

Volodymyr Huzii - Software Developer

About the Author

Volodymyr Huzii

Software Developer with 6+ years of full-stack experience, specializing in .NET, Vue.js, and modern web technologies. I focus on building highly secure, scalable, and performant software solutions that protect against modern cyber threats.

Skilled in developing secure SaaS applications, and integrating security best practices into every layer of the application stack. Expert in building applications that prioritize data protection and system integrity.

I work confidently across AWS and Azure environments, setting up secure CI/CD pipelines, and delivering robust, responsive, and high-performing applications with enterprise-grade security standards.

Strong collaborative mindset, proven ability to work with security teams and cross-functional teams, and a reputation for delivering secure solutions efficiently and reliably.

Safe Web Academy

Empowering individuals and organizations with cutting-edge cybersecurity knowledge and practical defense strategies.

© 2026 Safe Web Academy. All rights reserved. Securing the digital world.