Apache httpd: CVE status in November 2026

The Apache project released Apache HTTP Server 2.4.71 on November 11, 2026. The release addresses three CVEs. Apache rates CVE-2026-119618 in mod_http2 as critical: a synchronization flaw in assign_headers() can cause heap corruption and remote code execution (RCE).
Separately released mod_h2 versions 2.0.8 through 2.0.42 on GitHub are also affected. Those module releases use their own version numbering. Apache credits the discovery to Anthropic’s OSS Scanner and to Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research, among others.
Which releases include fixes?
The Apache security advisory list associates three CVEs with 2.4.71: CVE-2026-119618 (critical), CVE-2026-106023 in mod_md (important), and CVE-2026-109163 in mod_vhost_alias (low).
Earlier releases addressed 20 CVEs in 2.4.69 on October 1, 2026, 13 in 2.4.68 on June 8, 2026, and eleven in 2.4.67 on May 4, 2026. The list records five for 2.4.66 on December 4, 2025, one for 2.4.65 on July 23, 2025, and eight for 2.4.64 on July 10, 2025. Version 2.4.70 does not fix CVE-2026-119618; its changelog lists no CVE fixes.
The selection below lists affected upstream versions and the first release containing each fix. Exposure also depends on the modules in use, their configuration, and any distribution patches.
| CVE | Affected upstream versions | Fixed in | Apache rating | Summary |
|---|---|---|---|---|
| CVE-2026-119618 | 2.4.55–2.4.70 | 2.4.71 | critical | mod_http2: heap corruption, possible RCE |
| CVE-2026-57941 | 2.4.17–2.4.68 | 2.4.69 | moderate | mod_http2: use-after-free / wild write |
| CVE-2026-23918 | 2.4.66 | 2.4.67 | important | HTTP/2: double-free, possible RCE |
| CVE-2026-42535 | ≤ 2.4.67 | 2.4.68 | moderate | mod_dav_fs: access to DAV property databases |
| CVE-2025-23048 | 2.4.35–2.4.62 | 2.4.64 | moderate | mod_ssl: access control bypass through TLS 1.3 session resumption |
| CVE-2024-38475 | ≤ 2.4.59 | 2.4.60 | important | mod_rewrite: code execution or source disclosure; KEV |
| CVE-2026-63292 | 2.4.0–2.4.68 | 2.4.69 | moderate | mod_vhost_alias: stack buffer overflow |
| CVE-2026-93546 | ≤ 2.4.68 | 2.4.69 | moderate | mod_dav_fs: integer overflow in PROPPATCH |
Apache severity ratings and numerical CVSS scores are separate assessment systems. The NVD pages returned no usable scoring data during this review, so no CVSS scores are presented here as verified.
What is known about exploitation?
CVE-2024-38475 is listed in the CISA KEV dataset, version 2026.11.10. Other Apache httpd entries include CVE-2021-41773, CVE-2021-42013, and CVE-2019-0211. A KEV listing documents known exploitation; absence from the catalog does not establish that a vulnerability is safe.
Am I affected?
Check whether Apache httpd is actually running, which modules are loaded, and whether your distribution has already patched the relevant CVE. For distribution packages, the server version string alone is insufficient.
- Systems without Apache httpd: These httpd CVEs do not apply. The installed and running software still needs to be verified.
- Nextcloud AIO containers: Check the patch status of the specific image in use. Vendor management, automatic updates, or a container rebuild on November 12 do not establish that a CVE has been fixed.
- Apache Tika and apache2-utils: Tika is a separate project;
apache2-utilsprovides tools such ashtpasswd. Their presence alone does not imply a running httpd server. - Your own httpd server with HTTP/2: Vulnerable
mod_http2versions deserve priority because of the potential for RCE. Other loaded modules must still be checked for applicable CVEs when HTTP/2 is disabled.
The homelab’s overall patch status remains unconfirmed without verified package and image versions.
Update and verify the fix
For distribution packages, use the vendor’s security notices and package revisions to establish patch status. On Debian or Ubuntu, start with these checks:
# Check server version and loaded modules
apache2 -v
apache2ctl -M
# Depending on the installation: httpd -v / httpd -M
# Check installed package revisions and available versions
dpkg-query -W apache2 apache2-bin
apt-cache policy apache2 apache2-bin
# Refresh package lists and update installed packages
sudo apt update
sudo apt install --only-upgrade apache2 apache2-bin
Then check the relevant Debian or Ubuntu security notice to confirm that the installed package revision fixes the CVE. Reload or restart the service as instructed by the vendor so that the corrected code is running. Containers must be recreated from an image confirmed to contain the fix; restarting an old image is insufficient.
Apache provides the 2.4.71 source code for custom builds. This release includes the upstream fixes discussed here. It does not provide a general guarantee that an installation is secure.