
PEACH
Uma estrutura de isolamento de inquilino
CVE-2026-119618 is a race condition (Concurrent Execution using Shared Resource with Improper Synchronization) in Apache HTTP Server's mod_http2 module within the assign_headers() function that can lead to remote code execution (RCE). It affects Apache HTTP Server versions 2.4.55 through 2.4.70, and standalone mod_h2 GitHub releases from 2.0.8 through 2.0.42. The vulnerability was disclosed on November 11, 2026, with patches released the same day. It carries a CVSS v3.1 base score of 8.1 (High), reflecting network-based exploitation with no authentication or user interaction required, though attack complexity is rated High (Apache Advisory, GitHub Advisory).
The root cause is a race condition (CWE-362) combined with improper input validation (CWE-20) in the assign_headers() function of mod_http2. When a client sends a bodyless POST request with a Content-Type header but no Content-Length header and the END_STREAM flag set on the HEADERS frame, the function synthesizes a Content-Length: 0 value and writes it into a shared per-stream header table. This write races with concurrent reads by a different worker thread, causing heap corruption. The attack surface requires HTTP/2 to be enabled (h2 or h2c in the Protocols directive). Exploitation involves opening many parallel HTTP/2 connections and flooding streams with crafted header-heavy requests (typically 78+ filler headers to saturate the HPACK header table) to maximize the probability of hitting the race window. Public PoC tools confirm the heap corruption is reliably triggerable; at least one repository (studiogangster/CVE-2026-119618) claims to demonstrate actual RCE via a CGI handler path (Apache Advisory, GitHub Advisory).
Successful exploitation can result in full compromise of the affected Apache HTTP Server instance, with high impact to confidentiality, integrity, and availability. An unauthenticated remote attacker can execute arbitrary commands with the privileges of the web server process (typically www-data or apache), enabling data exfiltration, web shell deployment, lateral movement within the hosting environment, and denial of service via worker process crashes. Internet-facing servers with HTTP/2 enabled are directly exposed, and the vulnerability is particularly significant given Apache HTTP Server's widespread deployment across web hosting infrastructure (Apache Advisory, GitHub Advisory).
Multiple public proof-of-concept tools appeared on GitHub within 24 hours of disclosure, including scanners, crash PoCs, and at least one claimed RCE exploit (studiogangster/CVE-2026-119618) that targets a CGI handler path. Active in-the-wild exploitation has been reported by multiple sources including CyberSecurityNews and GBHackers, and Singapore's CSA issued an urgent patching advisory (CSA Alert, CyberSecurityNews). The EPSS score is approximately 0.40% (per Feedly data), though exploitation has been confirmed in the wild. The vulnerability is not yet listed in the CISA KEV catalog based on available data. Notably, the vulnerability was discovered with involvement from Anthropic and Google researchers (SecurityWeek).
h2) or cleartext upgrade (h2c) by sending an HTTP/2 preface and checking for a SETTINGS frame response.Server response header for the Apache version string matching the affected range (2.4.55–2.4.70). Passive scanners like foxcornlab/apache-httpd-scanner automate this step.Content-Type: application/x-www-form-urlencoded, no Content-Length header, and END_STREAM set on the HEADERS frame. Check server access logs or response behavior for evidence that assign_headers() synthesizes Content-Length: 0, confirming the vulnerable code path is reachable.Content-Type present, no Content-Length, END_STREAM set, and approximately 78 filler x-pad-NNN headers to fill the HPACK header table to capacity. Interleave with benign GET flood streams to saturate the worker pool.RST_STREAM (CANCEL) frames immediately after stream creation to race server-side stream cleanup. Repeat across multiple waves to maximize concurrency.mod_cgid, PHP, SSI), pass a command in the X-Cmd header or request body via the trigger stream. Capture command output from the X-Cmd-Out response header or response body to confirm arbitrary code execution as the web server process user (GitHub Advisory, Apache Advisory).Content-Type header, no Content-Length, and END_STREAM set on HEADERS frames; RST_STREAM frames with error code 0x8 (CANCEL) sent immediately after stream creation; GOAWAY frames with non-zero error codes from the server; outbound connections from the Apache process to unknown external IPs (potential reverse shell).access_log entries showing repeated bodyless POST requests to arbitrary paths with Content-Type but no Content-Length; error_log entries containing sanitizer markers (ASAN/TSAN/UBSAN) referencing assign_headers or heap corruption; abnormal child process crash/restart messages ([notice] child pid XXXX exit signal Segmentation fault)./bin/sh, bash, curl, wget, python); Apache worker processes consuming abnormally high memory or crashing repeatedly; CGI processes executing unexpected system commands.www-data or apache user; modified Apache configuration files enabling additional CGI handlers or modules.Primary remediation: Upgrade Apache HTTP Server to version 2.4.71 or later, which contains the fix (commit 824beab9b9424d6cfb29595248fdbf6c3dddeab1). For standalone mod_h2 from GitHub, upgrade to version 2.0.43 or later. Distribution-specific patches are available from Red Hat (RHSA-2026:98982, RHSA-2026:98968, RHSA-2026:100550), Ubuntu (USN-9090-1), SUSE (SUSE-SU-2026:5235-1), Amazon Linux (ALAS2023-2026-3458, ALAS2-2026-4114), and others (Apache Advisory, GitHub Advisory).
Workaround (if immediate patching is not possible): Disable HTTP/2 by removing h2 and h2c from the Protocols directive in Apache configuration:
Protocols http/1.1This eliminates the attack surface entirely. Verify the change is effective by confirming the server no longer negotiates HTTP/2 via ALPN. Additionally, implement network-level controls (WAF rules, rate limiting on concurrent HTTP/2 connections) to reduce exposure while patches are deployed (cPanel Advisory).
The vulnerability generated significant community attention immediately after disclosure. SecurityWeek reported that the flaw was discovered with involvement from Anthropic and Google researchers, which drew notable interest given the AI-assisted discovery angle (SecurityWeek). Security researcher GossiTheDog (@GossiTheDog on Mastodon) commented on the vulnerability shortly after disclosure. Wordfence published a PSA specifically for WordPress site owners given Apache's prevalence in WordPress hosting environments. Imperva, Wiz, Praetorian, Horizon3.ai, Sysdig, Orca Security, and F5 Labs all published technical analyses and customer advisories within 48 hours. There was notable debate in the community (covered by dugganusa.com) about the severity discrepancy between Red Hat's assessment and Wiz's analysis. The vulnerability trended heavily on Hacker News and across security-focused Mastodon instances, with Singapore's CSA issuing an urgent advisory urging immediate patching after active exploitation was confirmed (CSA Alert, SecurityWeek).
Corrija a disponibilidade entre as principais distribuições Linux e seus lançamentos.
bookworm
apache2: 2.4.71-1~deb12u1
sid
apache2: 2.4.71-1
trixie
apache2: 2.4.71-1~deb13u1
bionic (esm-infra)
apache2
devel
apache2: 2.4.68-1ubuntu8
focal (esm-infra)
apache2: 2.4.41-4ubuntu3.23+esm11
jammy
apache2: 2.4.52-1ubuntu4.27
noble
apache2: 2.4.58-1ubuntu8.19
resolute
apache2: 2.4.66-2ubuntu2.8
trusty (esm-infra-legacy)
apache2
xenial (esm-infra-legacy)
apache2
RHEL 8
RHEL 9
:appstream:mod_http2-0:2.0.26-2.el9_4.4.src
RHEL 10
mod_http2-0:2.0.29-2.el10_0.3.src
Origem: Este relatório foi gerado usando IA
Avaliação Gratuita de Vulnerabilidades
Avalie suas práticas de segurança em nuvem em 9 domínios de segurança para avaliar seu nível de risco e identificar lacunas em suas defesas.
Marque uma demonstração personalizada
"A melhor experiência do usuário que eu já vi, fornece visibilidade total para cargas de trabalho na nuvem."
"A Wiz fornece um único painel de vidro para ver o que está acontecendo em nossos ambientes de nuvem."
"Sabemos que se a Wiz identifica algo como crítico, na verdade é."