Critical RCE Vulnerability in Apache HTTP Server

A newly disclosed critical vulnerability (CVE-2026-119618) in Apache HTTP Server’s HTTP/2 module allows heap corruption that vendors say can be reliably exploited for remote code execution on default configurations. Commenters examine whether it’s appropriate to label memory corruption as RCE without a public exploit, note Red Hat’s claim of a working exploit and a CVSS score of 9.8, and point to disabling HTTP/2 as an effective mitigation until patched packages land. The thread also branches into broader themes: the growing role of AI tools in finding vulnerabilities, ongoing debates over Apache vs. nginx and HTTP/2’s complexity, and how language and concurrency choices (e.g., C vs. Rust) affect security.

Nature and Severity of the Vulnerability

  • Vulnerability is in Apache httpd’s HTTP/2 module (mod_http2 / mod_h2), due to an improper concurrency/threading interaction that can cause heap corruption.
  • Affects Apache 2.4.55–2.4.70 and mod_http2 2.0.8–2.0.42; HTTP/2 must be enabled and used.
  • Red Hat and Apache classify it as a critical RCE with CVSS 9.8; some commenters note Apache’s own advisory and Red Hat’s writeup assert reliable RCE is possible.

“Memory Corruption = RCE?” Debate

  • Some argue it’s misleading to label something RCE without a public exploit and suggest calling it just “memory corruption.”
  • Others reply that modern practice is to treat remotely triggerable memory corruption as exploitable by default, given historical experience and current exploit sophistication.
  • Red Hat claims a working RCE against default-configured servers; some commenters accept that as strong evidence even without a public PoC.

Mitigation and Practical Exposure

  • Disabling HTTP/2 (e.g., a2dismod http2) is widely cited as an effective mitigation; many report HTTP/2 is disabled by default on their Apache installations.
  • Some note that certain distros (e.g., some enterprise Linux versions) ship Apache versions too old to be affected, or with HTTP/2 off.
  • A few discuss operational gotchas when shutting down Apache (e.g., certbot/systemd restarting it) and suggest masking the service or firewalling ports.

AI’s Role in Discovery and Exploitation

  • Vulnerability reportedly discovered independently by two AI-using organizations; one commenter reproduces the bug via an LLM-guided search in minutes.
  • Opinions diverge: some see AI as just another analysis tool (like fuzzers), others worry about ethics, energy use, licensing, and low-quality AI-generated patches.

Apache vs. Alternatives (nginx, Caddy, Rust servers)

  • Thread revisits Apache vs nginx: performance now seen as similar; differences are mainly configuration style, module ecosystem, and features.
  • Apache’s .htaccess is praised for per-directory configurability, but others call it a misfeature and security risk; it is optional and can be disabled.
  • Several argue for memory-safe languages (e.g., Rust) to prevent this class of bug; others question whether a Rust rewrite would truly avoid such logic errors.

HTTP/2, HTTP/1.1, and HTTP/3

  • Some think HTTP/2’s complexity wasn’t worth it and expect HTTP/1.1 to outlive it; others report large latency gains, especially with many small assets.
  • HTTP/3 is criticized as TCP-over-UDP complexity with mixed real-world performance.