Summary
| Field | Detail |
|---|---|
| Release | Apache HTTP Server 2.4.71, published 2026-11-11, fixing all three CVEs |
| Advisories | Three CVEs, listed under Advisories |
| Headline | CVE-2026-119618 — a race in mod_http2’s assign_headers() corrupts the heap and can lead to remote code execution |
| Highest severity | CVE-2026-119618: critical (Apache’s rating); CISA’s ADP record scored it CVSS v3.1 8.1 (High) on 2026-11-13 |
| Types | A race leading to heap corruption (CWE-362), a NULL pointer dereference (CWE-476), and a one-byte stack buffer overwrite (CWE-121) |
| Who is exposed | A server that loads mod_http2 and serves HTTP/2 (h2 or h2c) on httpd 2.4.55 through 2.4.70, or one built with the standalone mod_h2 module 2.0.8 through 2.0.42 — see What each bug needs |
| KEV listed | no |
| Public exploit | none known |
Advisories
The Apache HTTP Server project’s 2.4 vulnerabilities page
and the 2.4.71 CHANGES file describe all three. Apache rates the bugs
on its own scale; the CVE records carry no CVSS score from Apache
itself. CISA’s ADP container has since added CVSS v3.1 scores for all
three: 8.1 (High) for CVE-2026-119618 on 2026-11-13, and 7.5 (High) for
CVE-2026-106023 and 5.9 (Medium) for CVE-2026-109163, both on
2026-11-17.
| CVE | Bug | CWE | Apache rating | Affects |
|---|---|---|---|---|
| CVE-2026-119618 | mod_http2: heap corruption and RCE in assign_headers | CWE-362 | critical | 2.4.55 – 2.4.70; mod_h2 2.0.8 – 2.0.42 |
| CVE-2026-106023 | mod_md NULL pointer dereference leads to child process crash | CWE-476 | important | 2.4.30 – 2.4.70 |
| CVE-2026-109163 | mod_vhost_alias 1 byte stack buffer overwrite (after CVE-2026-63292) | CWE-121 | low | 2.4.69 and 2.4.70 |
Not vulnerable: 2.4.71 and later. The 2.4 series is the only one Apache maintains, so there is no other upstream release to move to.
Apache credits CVE-2026-119618 to two independent finders: Anthropic’s OSS Scanner (reported 2026-10-26, as ANT-2026-MAPKT6MZ), and Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research (reported 2026-11-03).
- CVE-2026-106023 — hexb1n, Yang Song, and JiaSheng He of 360 Vulnerability Research Institute; Lucian Nitescu; and Bartlomiej Dmitruk at striga.ai.
- CVE-2026-109163 — Gustavo Aiello; Charles Vosburgh (the-vibe-dev); Wojciech Tatarski (CloudLinux / TuxCare); Oz Kaiser (@tatikoma); and Daisuke Hatakeyama (SYZD Research).
What each bug needs
- CVE-2026-119618 — mod_http2 loaded and HTTP/2 enabled with the
Protocolsdirective:h2over TLS, orh2cin cleartext. Apache describes it as improper synchronization between threads sharing a resource inassign_headers(). Wiz calls it a remote, unauthenticated route to code execution with the server process’s privileges. A host that builds the standalone mod_h2 module from GitHub instead of httpd’s bundled copy is affected from 2.0.8 through 2.0.42; mod_h2 had no fixed release at disclosure. - CVE-2026-106023 — mod_md, httpd’s ACME certificate manager, loaded. A request can make a child process dereference a NULL pointer and crash. That is a denial of service only.
- CVE-2026-109163 — mod_vhost_alias loaded, on 2.4.69 or 2.4.70 only. It writes one byte past a stack buffer, and Apache’s title says it came in with the fix for CVE-2026-63292.
Patch status
A row is Fixed once its httpd carries the fix for every one of the three CVEs that affects it: 2.4.71 or later, or a distribution package with the patches backported. A package with only some of the fixes stays vulnerable. A vulnerable row that builds an unpatched upstream release needs 2.4.71.
Current version is what the release ships today; First fixed is the first build that carried the fixes, and Fixed since the date it became available.
| Distribution | Release | Current version | First fixed | Fixed since | Status |
|---|---|---|---|---|---|
| Apache httpd | 2.4 series | 2.4.71 | 2.4.71 | 2026-11-11 | ✅ Fixed |
| Debian | sid (unstable) | 2.4.71-1 | 2.4.71-1 | 2026-11-11 | ✅ Fixed |
| Debian | forky (testing) | 2.4.71-1 | 2.4.71-1 | 2026-11-15 | ✅ Fixed |
| Debian | 13 (trixie) | 2.4.71-1~deb13u1 | 2.4.71-1~deb13u1 | 2026-11-12 | ✅ Fixed — DSA-6620-1 |
| Debian | 12 (bookworm) | 2.4.71-1~deb12u1 | 2.4.71-1~deb12u1 | 2026-11-12 | ✅ Fixed — DLA-4902-1 |
| pkgsrc | pkgsrc-current — www/apache24 | apache-2.4.71 | apache-2.4.71 | 2026-11-11 | ✅ Fixed |
| pkgsrc | pkgsrc-2026Q3 — www/apache24 | apache-2.4.71 | apache-2.4.71 | 2026-11-12 | ✅ Fixed |
| NixOS | nixos-unstable | 2.4.71 | 2.4.71 | 2026-11-18 | ✅ Fixed |
| NixOS | nixos-unstable-small | 2.4.71 | 2.4.71 | 2026-11-15 | ✅ Fixed |
| NixOS | nixos-26.05 | 2.4.71 | 2.4.71 | 2026-11-17 | ✅ Fixed |
| NixOS | nixos-26.05-small | 2.4.71 | 2.4.71 | 2026-11-16 | ✅ Fixed |
| nixpkgs | master branch | 2.4.71 | 2.4.71 | 2026-11-15 | ✅ Fixed |
| nixpkgs | release-26.05 branch | 2.4.71 | 2.4.71 | 2026-11-15 | ✅ Fixed |
| nixpkgs | nixpkgs-unstable | 2.4.71 | 2.4.71 | 2026-11-18 | ✅ Fixed |
Apache httpd
2.4 is the only series Apache maintains; a host building httpd from source needs a 2.4 release with the fixes. The fix commits are in the httpd repository (listed in the verification log).
Debian
The Debian security tracker is the authoritative
source for per-suite status; it carries a page per CVE. The source
package is apache2, and mod_http2, mod_md, and mod_vhost_alias all
ship as loadable modules in the apache2-bin binary package. None of
the three is in the set a fresh install enables, so an affected module
only runs once a2enmod has turned it on.
a2enmod http2 on its own turns HTTP/2 on server-wide: the module’s
configuration file carries Protocols h2 h2c http/1.1.
pkgsrc
The pkgsrc tree (NetBSD’s package collection, also used on SmartOS,
macOS via pkgin, and elsewhere) builds httpd from www/apache24, as
the package apache. mod_http2 is built under the http2 option,
which is on by default; mod_md only under the
apache-managed-domain-handling option, which is off by default.
pkgsrc-2026Q3, the current quarterly branch, receives fixes by
pull-up from pkgsrc-current.
The identifier carries an nbN suffix when the package’s
PKGREVISION is set. That revision bumps for many reasons besides
security patches — recursive bumps for shared-library ABI changes,
dependency and build-system tweaks — so an nbN suffix on its own
says nothing about these CVEs.
NixOS
nixpkgs builds httpd as apacheHttpd. On the unstable side the
expression is pkgs/by-name/ap/apacheHttpd_2_4/package.nix; the 26.05
release branch still keeps it at pkgs/servers/http/apache-httpd/2.4.nix.
The package builds mod_http2 by default.
The NixOS services.httpd module turns HTTP/2 on by default. A virtual
host’s http2 option defaults to true; while any host has it, the
module loads mod_http2, and it writes Protocols h2 h2c http/1.1 into
each such host’s TLS virtual host. So a NixOS host serving HTTPS from
the module is exposed to CVE-2026-119618 by default; a host serving
plain HTTP only loads the module without offering HTTP/2.
nixpkgs-unstable is the channel for Nix users outside NixOS — on
macOS or another Linux distribution. A channel row’s Fixed since is
the date that channel published its first release containing the fix;
a branch row’s is the date the fix was merged into that branch.
Flake users
A flake input such as github:NixOS/nixpkgs/nixos-unstable follows
the branch of that name, which moves with the channel — so the
channel’s row answers for it. An input on master or release-26.05
gets the fix as soon as it lands there, before any channel publishes
it.
Detection
Check the version. 2.4.71 or later is fixed; a distribution build is fixed only once the table above says so.
apachectl -v
Debian’s control script is apache2ctl, with apachectl as a link to
it; the server binary is httpd or apache2 depending on the system,
and -v on any of them prints the same version line.
Distribution packages keep the upstream version and bump their own revision for a backport. The installed package version is what to compare against the table — on Debian:
dpkg-query -W -f='${Version}\n' apache2-bin
On pkgsrc, where the identifier is apache-<version> plus an
nb<PKGREVISION> suffix when one is set:
pkg_info -e apache
On NixOS, apachectl -v from the system’s apacheHttpd reports the
version built into the closure; compare it with the channel’s row.
Whether the affected modules run at all depends on the configuration.
List the loaded modules and look for http2_module, md_module, and
vhost_alias_module:
apachectl -M
On NixOS, apachectl -M reads the package’s built-in default
configuration rather than the system’s; name the generated file
instead:
apachectl -f /etc/httpd/httpd.conf -M
A loaded http2_module is reachable over HTTP/2 only where a
Protocols directive names h2 or h2c. On Debian, search only the
enabled configuration — mods-available/ always holds the http2
module’s own Protocols line:
grep -Rn -i '^[[:space:]]*Protocols[[:space:]]' /etc/apache2/apache2.conf /etc/apache2/mods-enabled /etc/apache2/sites-enabled /etc/apache2/conf-enabled
pkgsrc keeps the configuration in ${PKG_SYSCONFDIR}
(/usr/pkg/etc/httpd by default); on NixOS, search
/etc/httpd/httpd.conf.
Mitigation
The real fix is httpd 2.4.71 or later, or a distribution package with
the patches. Until one is installed, Wiz suggests switching HTTP/2
off, which takes CVE-2026-119618 off the network. Set this in
the server configuration and drop h2 and h2c from every other
Protocols line:
Protocols http/1.1
On Debian, disabling the module altogether does the same:
a2dismod http2
On NixOS, set services.httpd.virtualHosts.<name>.http2 = false; on
every virtual host; the module then neither loads mod_http2 nor writes
the Protocols line.
A server that does not need mod_md or mod_vhost_alias can unload them
the same way (a2dismod md, a2dismod vhost_alias on Debian).
A configuration change does not change a row’s status above: only an httpd build with the fixes does.
Verification log
Every verdict in the table above is backed by a checkable source. This log records the provenance — the advisory, repository index, or git reference that established each fact — so any row can be audited or reproduced. Most readers never need it.
Full verification log
Upstream
- Apache 2.4 vulnerabilities page (httpd.apache.org):
- CVE-2026-119618 is rated critical. It affects 2.4.55 through 2.4.70
and mod_h2 2.0.8 through 2.0.42, was fixed in 2.4.x by
824beaband released in 2.4.71, both on 2026-11-11. It credits Anthropic’s OSS Scanner (reported 2026-10-26) and Google Cloud Vulnerability Research (reported 2026-11-03). - CVE-2026-106023 is rated important and CVE-2026-109163 low; both are fixed in 2.4.71.
- CVE-2026-119618 is rated critical. It affects 2.4.55 through 2.4.70
and mod_h2 2.0.8 through 2.0.42, was fixed in 2.4.x by
CHANGES_2.4(downloads.apache.org):- The “Changes with Apache 2.4.71” entries give the affected ranges (2.4.55–2.4.70; 2.4.30–2.4.70; 2.4.69 and 2.4.70).
- Each entry credits only the first finder the vulnerabilities page and the CVE record list; the page takes the full credits from those two.
- Release tarball (downloads.apache.org/httpd):
httpd-2.4.71.tar.bz2is dated 2026-11-11 10:13 — the upstream row’s Fixed since.- Current version is the newest
httpd-2.4.*.tar.bz2in the listing.
- Fix commits (named by the Debian security tracker’s notes):
824beab9b942(CVE-2026-119618),1b47e95c61fb(CVE-2026-106023),5566851a0649(CVE-2026-109163), inapache/httpd.
- mod_h2 (GitHub releases):
- The newest release is v2.0.42 (2026-05-29), inside the affected range; no release since carries the fix. Wiz contradicts itself on a fixed mod_h2 version, so this tracker takes Apache’s range and the release list instead.
- CVE records (the CVE Services API):
- All three published 2026-11-11 by the Apache Software Foundation, with Apache’s textual rating: CWE-362, CWE-476, and CWE-121.
- CISA’s ADP container scored CVE-2026-119618 CVSS v3.1 8.1
(
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) on 2026-11-13, with an SSVC assessment of Exploitation: none, Automatable: no, Technical impact: total. - CISA’s ADP container scored CVE-2026-106023 CVSS v3.1 7.5
(
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) on 2026-11-17, with an SSVC assessment of Exploitation: none, Automatable: yes, Technical impact: partial. - CISA’s ADP container scored CVE-2026-109163 CVSS v3.1 5.9
(
AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) on 2026-11-17, with an SSVC assessment of Exploitation: none, Automatable: no, Technical impact: partial.
- NVD (the NVD 2.0 API):
- CVE-2026-119618 is in status Modified, showing CISA’s score as a secondary metric; NVD has assigned no primary score of its own, and there is no CISA KEV entry.
- Wiz (2026-11-11 write-up):
- The source for the remote, unauthenticated code-execution impact
and the “no exploit is available” statement, and for the
Protocols http/1.1workaround; Apache’s entries give none.
- The source for the remote, unauthenticated code-execution impact
and the “no exploit is available” statement, and for the
Distributions
- Debian (security tracker per-CVE pages; Current version from
scripts/debian-versions):- All three pages list sid, forky, trixie (security), and bookworm (security) fixed, and trixie and bookworm vulnerable in their plain suites.
- sid and forky’s
2.4.71-1, trixie-security’s2.4.71-1~deb13u1, and bookworm-security’s2.4.71-1~deb12u1changelogs name all three CVEs; no other suite’s changelog names any. - trixie’s fix shipped as DSA-6620-1; the package first appeared in the security archive 2026-11-12 — trixie’s Fixed since.
- bookworm’s fix shipped as DLA-4902-1; the package first appeared in the security archive 2026-11-12 — bookworm’s Fixed since.
- snapshot.debian.org first saw
apache2_2.4.71-1.dscat 2026-11-11 14:32 UTC — sid’s Fixed since. - testing’s
Sourcesindex carried2.4.71-1by 2026-11-15 18:00 UTC but not yet at 12:00 UTC that day, per snapshot.debian.org — forky’s Fixed since. - The default module set is the
enable_default_moduleslist indebian/apache2.postinst(2.4.71-1), which names none ofhttp2,md, orvhost_alias.
- pkgsrc (local clone,
scripts/pkgsrc-versions):www/apache24onorigin/trunkandorigin/pkgsrc-2026Q3; the package name isDISTNAMEwithhttpdreplaced byapache. No patch names a tracked CVE.origin/trunkupdated to 2.4.71 in71a1b09aa02c, dated 2026-11-11 —pkgsrc-current’s Fixed since. The next commit,9817367ad42b, resetsPKGREVISION.origin/pkgsrc-2026Q3took 2.4.71 by pull-up ticket #7385 (b905145c2508, dated 2026-11-12) — Q3’s Fixed since.
- NixOS channels (local nixpkgs clone at each channel’s revision,
scripts/nixpkgs-versions):- nixos-unstable, nixos-unstable-small, and nixpkgs-unstable read
pkgs/by-name/ap/apacheHttpd_2_4/package.nix. nixos-26.05 and nixos-26.05-small readpkgs/servers/http/apache-httpd/2.4.nix. - No file in either directory names a tracked CVE.
scripts/nixos-first-shippednames nixos-unstable’s first fixed releasenixos-26.11pre1122823.04906337b6d5(2026-11-18) — that channel’s Fixed since.scripts/nixos-first-shippednames nixos-unstable-small’s first fixed releasenixos-26.11pre1121952.5da7db4ddb6d(2026-11-15) — that channel’s Fixed since.scripts/nixos-first-shippednames nixos-26.05’s first fixed releasenixos-26.05.14630.f68407657ad2(2026-11-17) — that channel’s Fixed since.scripts/nixos-first-shippednames nixos-26.05-small’s first fixed releasenixos-26.05.14584.c22eb062fe0b(2026-11-16) — that channel’s Fixed since.scripts/nixos-first-shippednames nixpkgs-unstable’s first fixed releasenixpkgs-26.11pre1122334.e21fec321d73(2026-11-18) — that channel’s Fixed since.
- nixos-unstable, nixos-unstable-small, and nixpkgs-unstable read
- nixpkgs branches (local clone):
- Current version from
scripts/nixpkgs-versions branch:master, and with-d/-eforbranch:release-26.05. - master’s bump to 2.4.71 landed via
d4a0d6baf111(#587162), merged 2026-11-15 — that branch’s Fixed since. - release-26.05’s backport to 2.4.71 landed via
35c96487dc13(#588747), merged 2026-11-15 — that branch’s Fixed since. nixos/modules/services/web-servers/apache-httpdon master: the vhosthttp2option defaults totrue; any vhost with it set loadshttp2globally, and each such vhost’s TLS<VirtualHost>getsProtocols h2 h2c http/1.1. The plain-HTTP block gets none.
- Current version from
- NixOS security tracker (tracker.security.nixos.org) — a JS-rendered application; linked for readers, not read by this tracker.