StackX Apache
The parade of backports continues! And now it’s the Apache web server’s turn. Back in May, a vulnerability affecting Apache through HTTP/2 had required a mitigation on legacy servers: disabling HTTP/2 support. Debian 11 (Bullseye), meanwhile, was still maintained by Debian.
A few days ago: all hands on deck with CVE-2026-119618! After disabling HTTP/2 on Debian 11 Bullseye, and after the latest backports for PHP, Proxmox and the Linux kernel, I thought: why not Apache?
For this vulnerability, Apache describes memory corruption in mod_http2, affecting versions 2.4.55 through 2.4.70, which can lead to code execution: neither funny nor reassuring!
I used the build pipeline put in place for the previous patches to prepare patched Apache packages for Debian 9 Stretch, Debian 10 Buster and Debian 11 Bullseye, on amd64.
We’re not talking about just this one fix, but no fewer than 158 security fixes across the three distributions, Debian 9, 10 and 11.
These fixes are now integrated and available in our repositories as StackX Apache. The final sources cover CVE-2026-119618, the other flaws retained after LTS support ended for each branch, and the applicable regressions.
On 18 November 2026, all our clients’ machines running legacy versions of StackX based on Debian Stretch, Buster and Bullseye were updated! As with the previous patches, I decided to share the work with you: the details are below.
Debian 12 Bookworm and Debian 13 Trixie received the Debian fix on 12 November 2026: apache2 2.4.71-1~deb12u1 (DLA-4902-1) and apache2 2.4.71-1~deb13u1 (DSA-6620-1). No StackX Apache package is published for Bookworm or for Trixie.
See also StackX PHP and the StackX kernels, for the same three Debian releases, and StackX PX, for Proxmox VE 8 on Bookworm.
Revisions · Add the repository · Update procedure · CVE list
Published revisions
| Distribution and base | StackX revision |
|---|---|
| Debian 9 Stretch Base: 2.4.25-3+deb9u26 |
2.4.25-3+deb9u26+sx2 |
| Debian 10 Buster Base: 2.4.59-1~deb10u10 |
2.4.59-1~deb10u10+sx7 |
| Debian 11 Bullseye Base: 2.4.71-1~deb11u1 |
2.4.71-1~deb11u1+sx3 |
Each channel publishes the amd64 binaries, the source package, the Packages and Sources indexes, the SHA-256 sums and the add-stackx-apache-repo.sh script. The three InRelease indexes are signed with the historical StackX key:
AF97 ED98 AACE 4CE1 29A0 3B6E 2C97 36B5 93BA BF7FThe three final StackX sources are rebuilt from the official signed Apache archives and the public Debian Salsa commits: Stretch, Buster and Bullseye.
No package or file from Freexian’s private ELTS repository is used as input to these builds or republished here. Freexian provides a commercial ELTS service with a private APT repository. Its public advisories and sources accessible for reading were used only to compare the history.
Upstream fixes and StackX additions
Upstream Apache fixes and Debian packaging changes keep their attribution. The StackX work covers applicability, adaptations, hardening, building and testing.
The additional regressions and hardening cover, in particular, mod_proxy, mod_rewrite, mod_dav, mod_ssl, mod_cache, mod_substitute, provisional statuses and WebSocket paths. They stay distinct from the CVEs in the inventory.
On Stretch and Buster, the shared patches fix the mod_proxy_http2 fallback after failure (PR 69624) and the mod_proxy_balancer sticky route (PR 69443). Buster adds an addressTTL fix (PR 69126), ACME/ARI adaptations, TLS adaptations and provisional status lines. Stretch adds the functional WebSocket backport and the HTTP/2 method guard. Bullseye starts from Apache 2.4.71. The StackX additions on this branch mainly target the WebSocket paths and the version banner. These examples do not get a new CVE number.
Stretch carries the Apache version number 2.4.25, with a newer mod_http2 import in that base. CVE-2026-119618, which Apache indicates for 2.4.55 through 2.4.70, is therefore covered in this source despite the apparent version number. Buster 2.4.59 receives a patch in its source. Bullseye 2.4.71 contains the upstream fix. The three final sources cover this CVE. The upstream number does not say which VirtualHosts are exposed, nor which binary is loaded on a host.
Two CVEs older than the date window have specific StackX adaptations on Stretch: CVE-2019-17567 on the old WebSocket tunnel, and CVE-2021-33193 on HTTP/2 method validation. Legitimate ws:// and wss:// WebSockets over HTTP/1.1 stay in place. This Stretch base does not provide the HTTP/2 WebSocket from RFC 8441. An invalid 101 negotiation is rejected.
For CVE-2019-17567, Buster already inherits the Debian fix 2.4.59-1~deb10u1, and Bullseye the corrected upstream source. The StackX adaptations on these two branches also prevent a return to the old tunnel path, in the WebSocket configurations that were tested. For CVE-2021-33193, Buster and Bullseye inherit upstream code that is already fixed.
On Buster and Bullseye, WebSocket routes require mod_proxy_http. The directive ProxyWebsocketFallbackToProxyHttp Off does not bring the old direct tunnel path back. Custom module-loading configurations have to be checked. The mechanism is documented in mod_proxy_wstunnel.
CVE inventory
The figures start from the Apache HTTP Server 2.4 security bulletin, compared with the final sources and the patches actually applied. They count CVEs published after Debian LTS support ended for each distribution, then classify them against the StackX source. The year in the CVE number is not necessarily the year of publication. The total does not count exposed machines.
| Channel | Examined | Covered |
|---|---|---|
| Stretch | 83 | 70 |
| Buster | 72 | 65 |
| Bullseye | 23 | 23 |
- Stretch: 67 CVEs covered by patches and 3 fixes through the
mod_http2import. The other 13 cases are excluded: absent component (5), different platform (5), excluded upstream version range (3). - Buster: 65 CVEs covered by patches. The other 7 cases are excluded: different platform (5), excluded upstream version range (2).
- Bullseye: 23 CVEs covered by the Apache 2.4.71 source. No cases excluded within this filter; the presence of the fixes does not establish that the previous Bullseye revision was exposed to each of these flaws.
A fix present in the final source does not, by itself, prove that the module is enabled, that the package is installed, or that this binary is the one answering. A CVE set aside because its component is absent, its platform is different, or its upstream range does not match stays out of the fix lists. The same identifier can be in one channel’s source and set aside on another: the classification follows the channel.
Tests, revision and banner
Isolated tests of the final packages covered installation, dependencies, exact versions, modules and APT signatures. They also covered HTTP/1.1 cases, TLS, HTTP/2 on several VirtualHosts, forms, file uploads, WebSocket, proxy, FastCGI, reload and rollback.
These tests validate the listed cases. They do not validate every application or every VirtualHost in the fleet.
The installed revision is read locally with:
dpkg-query -W apache2 apache2-bin apache2-data apache2-utilsDepending on the distribution, the expected revisions are 2.4.25-3+deb9u26+sx2, 2.4.59-1~deb10u10+sx7 and 2.4.71-1~deb11u1+sx3.
With ServerTokens Full, an HTTP response produced by Apache adds ScalarX/ followed by the full revision to the Server field. On Stretch, the addition is ScalarX/2.4.25-3+deb9u26+sx2. Buster and Bullseye follow the same pattern with their revision. This setting is global and deliberate, and it says more about the components. The package does not enable it.
apachectl -V prints the base Apache version. The ScalarX token is checked in the HTTP response, not with this command. A proxied response may keep the backend banner. A load balancer does not prove that every node carries the same revision.
Add the repository for the right channel
Download the script for the distribution that is actually running, read it, then run it as root.
Debian 9 Stretch
curl -fsSLo add-stackx-apache-repo.sh https://mirrors.scalarx.net/stackx-apache/stretch/add-stackx-apache-repo.sh
less add-stackx-apache-repo.sh
bash add-stackx-apache-repo.shDebian 10 Buster
curl -fsSLo add-stackx-apache-repo.sh https://mirrors.scalarx.net/stackx-apache/buster/add-stackx-apache-repo.sh
less add-stackx-apache-repo.sh
bash add-stackx-apache-repo.shDebian 11 Bullseye
curl -fsSLo add-stackx-apache-repo.sh https://mirrors.scalarx.net/stackx-apache/bullseye/add-stackx-apache-repo.sh
less add-stackx-apache-repo.sh
bash add-stackx-apache-repo.shThe script adds only that channel’s APT source, then refreshes APT. It checks the distribution, the key, the signature and the index. It does not install Apache and it does not restart the service.
The script published for Stretch is adapted for GnuPG 2.1.18. The SHA-256 of the public file is:
2fd95526e67681ad97503912e5e7e2de02d6f1c300f29d7c24cbb12ec192e731Unlike the StackX PX repository, these Apache repositories are not NotAutomatic. An ordinary apt upgrade may offer the packages.
Simulate, install, check
Before updating, keep the configuration and the DEB files for the exact previous revisions installed. Also record the loaded modules, VirtualHosts and WebSocket routes. You need those items available before you need to roll back.
dpkg-query -W apache2 apache2-bin apache2-data apache2-utils
apache2ctl -M
apache2ctl -S
apache2ctl configtestThe repository script has already refreshed its channel’s index. Check the versions offered:
apt-cache policy apache2 apache2-bin apache2-data apache2-utilsAs root, run only the simulation for your distribution. It selects the four runtime packages together, at the exact revision:
Debian 9 Stretch
apt-get --simulate --no-remove install \
apache2=2.4.25-3+deb9u26+sx2 apache2-bin=2.4.25-3+deb9u26+sx2 \
apache2-data=2.4.25-3+deb9u26+sx2 apache2-utils=2.4.25-3+deb9u26+sx2Debian 10 Buster
apt-get --simulate --no-remove install \
apache2=2.4.59-1~deb10u10+sx7 apache2-bin=2.4.59-1~deb10u10+sx7 \
apache2-data=2.4.59-1~deb10u10+sx7 apache2-utils=2.4.59-1~deb10u10+sx7Debian 11 Bullseye
apt-get --simulate --no-remove install \
apache2=2.4.71-1~deb11u1+sx3 apache2-bin=2.4.71-1~deb11u1+sx3 \
apache2-data=2.4.71-1~deb11u1+sx3 apache2-utils=2.4.71-1~deb11u1+sx3Review the plan on your own server: dependencies, changed packages, any removals and consistent revisions. If APT wants to remove a package or mix revisions, stop the procedure. Validate the optional modules already installed separately.
If the plan is suitable, run the same command, removing only --simulate and keeping --no-remove and all four exact versions. Install during the planned maintenance window: package configuration scripts may reload or restart Apache. The statement above that nothing is installed or restarted applies only to the repository setup script.
After installation, check the versions again with dpkg-query, run apache2ctl configtest and check the modules, VirtualHosts and logs. Plan any reload or restart needed, then test HTTP/1.1, TLS, forms, file uploads, WebSockets and your applications. An installed package alone does not establish which version the running process is executing. Re-enable HTTP/2 after validating the VirtualHosts concerned.
To roll back, restore the four packages to their exact previous revisions and restore the saved configuration. First simulate that operation using a trusted repository, check the dependencies and that the set is consistent, then apply it during a planned window. Do not leave a mixture of revisions. Check the modules too: reverting the packages does not automatically restore their previous state.
Scope
These packages cover Apache and the components published in the three amd64 channels. This repository is not a general resumption of support for Debian 9, 10 or 11.
Re-enabling HTTP/2 must be validated on the relevant VirtualHosts and applications after the update.
Resources
- Apache HTTP Server 2.4 security bulletin
- CVE-2026-119618
- CVE-2019-17567
- CVE-2021-33193
- Debian starting source, Stretch
- Debian starting source, Buster
- Debian starting source, Bullseye
- DLA-4902-1, apache2 2.4.71-1~deb12u1
- DSA-6620-1, apache2 2.4.71-1~deb13u1
- Apache
ServerTokensdocumentation - Apache
mod_proxy_wstunneldocumentation - PR 69624,
mod_proxy_http2fallback - PR 69443,
mod_proxy_balancersticky route - PR 69126,
addressTTL - StackX Apache mirror
Other StackX contributions
- StackX PHP: maintenance and fixes for Debian 9, 10 and 11
- StackX kernels: native fixes and Linux 6.12 LTS for Debian 9, 10 and 11
- StackX PX: targeted security fixes for Proxmox VE 8
Appendix: CVEs by channel and excluded cases
Debian 9 Stretch, 2.4.25-3+deb9u26+sx2: 70 CVEs in the filter, plus CVE-2019-17567 and CVE-2021-33193
Of these 70: 67 CVEs covered by patches, and 3 fixes via the mod_http2 import.
2006 identifiers (1): CVE-2006-20001.
2022 identifiers (2): CVE-2022-36760, CVE-2022-37436.
2023 identifiers (5): CVE-2023-25690, CVE-2023-31122, CVE-2023-38709, CVE-2023-43622, CVE-2023-45802.
2024 identifiers (14): CVE-2024-24795, CVE-2024-27316, CVE-2024-36387, CVE-2024-38473, CVE-2024-38474, CVE-2024-38475, CVE-2024-38476, CVE-2024-38477, CVE-2024-39573, CVE-2024-39884, CVE-2024-40725, CVE-2024-42516, CVE-2024-43204, CVE-2024-47252.
2025 identifiers (7): CVE-2025-23048, CVE-2025-49630, CVE-2025-49812, CVE-2025-53020, CVE-2025-58098, CVE-2025-65082, CVE-2025-66200.
2026 identifiers (41): CVE-2026-109163, CVE-2026-119618, CVE-2026-24072, CVE-2026-28780, CVE-2026-29167, CVE-2026-29169, CVE-2026-29170, CVE-2026-33006, CVE-2026-33007, CVE-2026-33523, CVE-2026-33857, CVE-2026-34032, CVE-2026-34059, CVE-2026-34355, CVE-2026-34356, CVE-2026-42356, CVE-2026-42528, CVE-2026-42535, CVE-2026-42536, CVE-2026-43951, CVE-2026-44119, CVE-2026-44185, CVE-2026-44186, CVE-2026-44631, CVE-2026-46729, CVE-2026-47360, CVE-2026-48005, CVE-2026-48913, CVE-2026-49975, CVE-2026-56153, CVE-2026-56154, CVE-2026-57941, CVE-2026-58415, CVE-2026-59797, CVE-2026-63045, CVE-2026-63292, CVE-2026-63686, CVE-2026-73636, CVE-2026-73637, CVE-2026-79768, CVE-2026-93546.
Outside these 70, two CVEs older than the window have specific StackX adaptations: CVE-2019-17567 and CVE-2021-33193.
Debian 10 Buster, 2.4.59-1~deb10u10+sx7: 65 CVEs in the filter
65 CVEs covered by patches in the final source.
2024 identifiers (12): CVE-2024-36387, CVE-2024-38473, CVE-2024-38474, CVE-2024-38475, CVE-2024-38476, CVE-2024-38477, CVE-2024-39573, CVE-2024-39884, CVE-2024-40725, CVE-2024-42516, CVE-2024-43204, CVE-2024-47252.
2025 identifiers (8): CVE-2025-23048, CVE-2025-49630, CVE-2025-49812, CVE-2025-53020, CVE-2025-55753, CVE-2025-58098, CVE-2025-65082, CVE-2025-66200.
2026 identifiers (45): CVE-2026-106023, CVE-2026-109163, CVE-2026-119618, CVE-2026-24072, CVE-2026-28780, CVE-2026-29167, CVE-2026-29168, CVE-2026-29169, CVE-2026-29170, CVE-2026-33006, CVE-2026-33007, CVE-2026-33523, CVE-2026-33857, CVE-2026-34032, CVE-2026-34059, CVE-2026-34355, CVE-2026-34356, CVE-2026-42356, CVE-2026-42528, CVE-2026-42535, CVE-2026-42536, CVE-2026-43951, CVE-2026-44119, CVE-2026-44185, CVE-2026-44186, CVE-2026-44631, CVE-2026-46729, CVE-2026-47360, CVE-2026-48005, CVE-2026-48913, CVE-2026-49975, CVE-2026-56153, CVE-2026-56154, CVE-2026-56449, CVE-2026-57941, CVE-2026-58415, CVE-2026-59797, CVE-2026-63045, CVE-2026-63292, CVE-2026-63686, CVE-2026-63718, CVE-2026-73636, CVE-2026-73637, CVE-2026-79768, CVE-2026-93546.
Debian 11 Bullseye, 2.4.71-1~deb11u1+sx3: 23 CVEs fixed in the Apache 2.4.71 source
The fixes for these 23 CVEs are included in the Apache 2.4.71 source. The StackX additions on this branch mainly target the WebSocket paths and the version banner.
2026 identifiers (23): CVE-2026-106023, CVE-2026-109163, CVE-2026-119618, CVE-2026-42356, CVE-2026-42528, CVE-2026-46729, CVE-2026-47360, CVE-2026-48005, CVE-2026-56153, CVE-2026-56154, CVE-2026-56449, CVE-2026-57941, CVE-2026-58415, CVE-2026-59685, CVE-2026-59797, CVE-2026-63045, CVE-2026-63292, CVE-2026-63686, CVE-2026-63718, CVE-2026-73636, CVE-2026-73637, CVE-2026-79768, CVE-2026-93546.
Cases set aside, outside the counted fixes
Stretch, component absent from this source (5): CVE-2023-27522, CVE-2025-55753, CVE-2026-106023, CVE-2026-29168, CVE-2026-63718.
Stretch and Buster, platform path excluded on Linux amd64 (5): CVE-2024-38472, CVE-2024-40898, CVE-2024-43394, CVE-2025-59775, CVE-2026-59685.
CVE-2026-59685 is among Bullseye’s 23, because its fix is included in the Apache 2.4.71 source. On Stretch and on Buster, this platform path is excluded for Linux amd64: it does not enter their fixes.
Stretch, upstream Apache range not applicable (3): CVE-2025-54090, CVE-2026-23918, CVE-2026-56449.
Buster, upstream Apache range not applicable (2): CVE-2025-54090, CVE-2026-23918.
Sources and components keep their original licences and attribution.
--
Christophe Casalegno
https://all.bo