STACKIT-2026-004: Critical Vulnerability in Apache HTTP Server HTTP/2 Handling
Last updated on
Advisory metadata
Section titled “Advisory metadata”| Attribute | Value |
|---|---|
| Advisory ID | STACKIT-2026-004 |
| Published date | 2026-11-12 |
| Severity | Critical |
| Affected service | Self-managed Apache HTTP Server workloads / STACKIT-managed services not affected |
Overview
Section titled “Overview”A critical thread-safety vulnerability in the Apache HTTP Server HTTP/2 module (mod_http2) was disclosed on 2026-11-12 (CVE-2026-119618). The flaw is caused by concurrent processing without proper synchronization in the assign_headers() function during the handling of incoming HTTP/2 frames. The vulnerability affects Apache HTTP Server versions 2.4.55 through 2.4.70 as well as standalone mod_h2 releases from 2.0.8 through 2.0.42. Only server instances with the HTTP/2 protocol enabled through directives such as Protocols h2 h2c, Protocols h2, or Protocols h2c are affected; configurations that serve exclusively HTTP/1.1 are not affected.
Exploitation of this vulnerability allows unauthenticated remote threat actors to send specially crafted HTTP/2 frames over the network, triggering heap memory corruption that can result in arbitrary code running within the web server worker process or a denial of service through a process crash. As of 2026-11-12, no exploitation of this vulnerability on STACKIT infrastructure is known. The vulnerability is resolved in Apache HTTP Server 2.4.71 and in corresponding Linux distribution security updates. If immediate package updating is not possible, administrators can mitigate the vulnerability by disabling the HTTP/2 protocol through the configuration directive Protocols http/1.1 or by unloading mod_http2.
STACKIT evaluated its platform services and confirmed that STACKIT-managed services are not affected by this vulnerability. Customers using STACKIT-managed services do not have to take any action; this bulletin is updated as significant changes or additional information become available. Customers who operate self-managed systems running Apache HTTP Server must install the vendor or distribution updates directly or apply the recommended configuration mitigations. In addition, customers operating self-managed systems must review and restrict network access to their web servers until updates are complete to strengthen protection against this vulnerability.
Affected versions
Section titled “Affected versions”The vulnerability affects the following Apache HTTP Server and module versions when HTTP/2 is enabled (Protocols h2 h2c, Protocols h2, or Protocols h2c):
- Apache HTTP Server versions
2.4.55through2.4.70 - Standalone
mod_h2releases from2.0.8through2.0.42 - Operating system distribution packages based on affected upstream versions
Configurations running Apache HTTP Server < 2.4.55, systems that serve exclusively HTTP/1.1 (Protocols http/1.1), or instances where mod_http2 is not loaded are not affected by this vulnerability.
Identified CVEs
Section titled “Identified CVEs”The advisory addresses the following Common Vulnerabilities and Exposures (CVEs):
Required actions
Section titled “Required actions”Self-managed systems
Section titled “Self-managed systems”- Inspect server configurations and loaded modules: Identify all virtual machines and container workloads running Apache HTTP Server (
httpdorapache2). Check the installed version and determine whethermod_http2is active (for example, withhttpd -V,apache2 -V, orhttpd -M | grep http2). - Review protocol directives: Search configuration files (such as
httpd.conf,apache2.conf, or files withinconf.d/andconf-enabled/) for theProtocolsdirective. Ifh2orh2cis specified, the server is vulnerable. - Apply vendor security updates:
- Update Apache HTTP Server to version ≥
2.4.71or install the latest security updates provided by your operating system distribution. - Verify installed package versions against your Linux distribution security advisory.
- Update Apache HTTP Server to version ≥
- Apply temporary mitigations if patching is delayed:
- Disable HTTP/2 protocol: In the global server configuration or inside specific virtual host containers, configure the
Protocolsdirective to allow onlyHTTP/1.1:Protocols http/1.1 - Unload the module: If HTTP/2 capabilities are not required, comment out or remove the module loading directive for
mod_http2:On Debian or Ubuntu systems, disable the module using# LoadModule http2_module modules/mod_http2.soa2dismod http2. - Restart the web server service to apply the configuration changes (for example,
systemctl restart httpdorsystemctl restart apache2).
- Disable HTTP/2 protocol: In the global server configuration or inside specific virtual host containers, configure the
- Restrict network access: Restrict network access to self-managed web servers and administrative endpoints to trusted networks and authorized clients until updates are completed.
STACKIT-managed services
Section titled “STACKIT-managed services”- Platform services not affected: STACKIT evaluated its platform services and verified that STACKIT-managed services do not use vulnerable Apache HTTP Server HTTP/2 configurations.
- No customer action required: Customers using STACKIT-managed services do not need to take any action.
References
Section titled “References”- CVE Record: CVE-2026-119618
- Apache HTTP Server Project: Apache HTTP Server 2.4 vulnerabilities
Contact and support
Section titled “Contact and support”For questions regarding this advisory or assistance with system configuration, contact STACKIT Support:
- Open a ticket through the STACKIT Help Center.
- Contact the support team by email at
cybersecurity@stackit.cloud.