← 返回列表

HTTPd (CVE-2026-119618): Detecting heap corruption and RCE in Apache HTTP Server mod_http2

单站 Sysdig Blog 发布 Fri, 13 Nov 2026 00:00:00 GMT 入库 2026-11-18T05:37:43

HTTPd (CVE-2026-119618): Detecting heap corruption and RCE in Apache HTTP Server mod_http2

Get security briefings from the Threat Research Team

New campaigns, attacker techniques, and detection guidance — straight to your inbox.

Subscribe

Falco Feeds extends the power of Falco by giving open source-focused companies access to expert-written rules that are continuously updated as new threats are discovered.

learn more

Green background with a circular icon on the left and three bullet points listing: Automatically detect threats, Eliminate rule maintenance, Stay compliant, with three black and white cursor arrows pointing at the text.

On November 11, 2026, Apache released HTTP Server 2.4.71 to fix CVE-2026-119618, a critical severity heap corruption flaw in mod_http2 that Apache’s security advisory said can lead to remote code execution (RCE). The flaw sits in assign_headers(), affects versions 2.4.55 through 2.4.70, and can be triggered over HTTP/2 with no authentication. Red Hat and Amazon have scored the vulnerability 9.8 on CVSS v3.1, though CISA rates it at 8.1.

Two teams found the bug independently, eight days apart. Anthropic's OSS Scanner is an opt-in, model-driven scanner for open-source projects. It reported the bug on October 26, 2026. Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research reported it eight days later on November 3, according to the CVE record.

The day after Apache disclosed it on oss-security, a public proof-of-concept (PoC) was published on GitHub showing the heap corruption, though no PoC has been released for the RCE as of the publication of this blog. Additionally, no confirmed in-the-wild exploitation has been reported, and the CVE does not appear in CISA's KEV catalog.

The bug lives in Apache's own HTTP/2 implementation, not in any application the server hosts. Only servers that enable HTTP/2 are exposed. Affected organizations are encouraged to upgrade to version 2.4.71 or turn off HTTP/2 if patching is delayed.

The Sysdig Threat Research Team (TRT) analyzed the publicly available research and simulated a successful exploit to help defenders understand four key details: who is affected, what has been demonstrated versus claimed, what runtime visibility can detect, and what mitigation steps should be taken until a patch can be applied. They also tested and found that Sysdig’s existing runtime detections caught every post-exploitation step.

Timeline

Affected Apache HTTP Server versions

The flaw is in mod_http2, the HTTP/2 module of Apache HTTP Server. The same module is released separately as mod_h2 on GitHub and also affected.

While the Apache advisory rates the vulnerability as critical. The CVE record, which Apache maintains as the CVE Numbering Authority (CNA), doesn’t actually carry an associated CVSS score. However, Red Hat and Amazon both rate the vulnerability as critical and score it at 9.8 on CVSS v3.1 and CISA rates it as a high severity vulnerability at 8.1 on CVSS v3.1.

Red Hat rates its own RHEL 9 and 10 builds Important rather than Critical. Those builds allocate each HTTP/2 stream from "a separate allocator, which substantially increases the complexity of exploiting the flaw."

The severity and prioritization of this vulnerability in an organization’s environment depends first on whether HTTP/2 is on.

The version number alone won’t confirm exposure, check these additional factors:

How the HTTPd RCE flaw works

HTTP/2 carries many requests over one connection as parallel streams and that concurrency is where this flaw lies.

The Apache advisory calls the flaw "Concurrent Execution using Shared Resource with Improper Synchronization" in assign_headers(), and the CVE record lists CWE-362. Red Hat lists CWE-20 instead. Red Hat describes the root cause as "a worker thread writes into memory owned by the connection thread through a shared, lock-free allocator." In practice, two threads can corrupt the same heap.

The fix is a one-line change in assign_headers(). Before the fix, a request with a content type that had already ended had its zero Content-Length header written into the HTTP/2 request's own header table (req->headers). The fix writes it into the per-request table (r->headers_in) instead. The commit message gives no explanation. Red Hat's statement supplies the threading context.

What is reachable

Exposure depends on configuration. Red Hat states that only servers with HTTP/2 enabled through the Protocols directive are affected:

Red Hat's Bugzilla entry says an unauthenticated attacker triggers the flaw "by sending specially crafted HTTP/2 frames." That puts internet-facing, HTTP/2-enabled httpd in the first patch tier. This table does not cover reverse proxies in front of httpd.

HTTPd RCE exploitation: What's been demonstrated vs. claimed

According to Red Hat’s CVE page, public research has shown "a reliable exploit against a default-configured server." However, without a researcher name or links to details, this can’t be verified. As of the publishing of this blog, no other security researchers or vendors have confirmed exploitation.

As of about 16:00 UTC on November 12, a GitHub search for the CVE returned four repositories: a proof of concept, a patch-status tracker, and two detection or assessment tools.

The PoC reports heap corruption, not code execution. Its README describes the impact as "Heap corruption in an httpd child process; potential remote code execution."

Its evidence comes from a lab build:

The README doesn't show control of the corrupted memory, and the author has published no exploit.

The bottom line is that unauthenticated HTTP/2 traffic can crash and corrupt the heap of a vulnerable httpd. Remote code execution is possible, but nobody has publicly demonstrated it yet. Treat the crash as likely wherever HTTP/2 is on, and code execution as a credible risk.

HTTPd RCE impact

Nothing publicly disclosed as of November 13, 2026, shows in-the-wild exploitation, a mass-scanning campaign, or a public RCE exploit. The primary sources do establish the following:

Detecting HTTPd RCE with Sysdig Secure

Sysdig Secure customers have three layers of coverage for CVE-2026-119618. Threat Intelligence entries show where affected Apache hosts are running, Vulnerability Management maps to each distribution’s vendor advisory, and Runtime Detections catch what a successful exploit does once an attacker enters a vulnerable environment.

Threat intelligence

Sysdig Secure customers have two entries for CVE-2026-119618 in the Threat Intelligence feed. Each entry lists the affected hosts and running Kubernetes workloads. One entry uses the SBOM to find affected versions of Apache HTTP Server, mod_http2, and the vendor packages that contain the module. The other entry lists the assets where Sysdig Vulnerability Management reports the CVE.

Vulnerability management

Sysdig vulnerability management detects CVE-2026-119618 across your environment. To prioritize remediation, start with internet-facing workloads and packages in use at runtime.

Sysdig vulnerability scanning reports this CVE by distribution and release, and each status follows the vendor's own advisory. Rows move from "Waiting on vendor fix" to "Reported" as vendors publish fixes and the feed picks them up. The table reflects status as of November 13, 2026. On SaaS, vulnerability database updates reach scanners automatically, so new advisories need no scanner upgrade.

Runtime detection

The Sysdig TRT simulated a successful exploit inside a vulnerable Apache server, both inside a container and as a host service. Existing runtime threat detections caught every step without rule modifications, including:

A successful attack would give the attacker code execution as the httpd worker. From there, attackers do what they do after any web server RCE: open a reverse shell, download and run a tool, start a miner, steal cloud credentials, or try a kernel local privilege escalation.

Detecting HTTPd RCE with open source Falco

Falco sees syscalls, not HTTP/2 frames. It cannot see the malicious request itself, but it can see what the request causes on the host. That includes a shell or unexpected binary spawned by an httpd process, an unexpected outbound connection, or a write to a sensitive path.

Web servers fork helpers legitimately, so rules scoped to httpd need tuning to stay quiet. The post-exploitation strategies above apply.

Recommendations

Patch

Interim mitigations if you cannot patch today

Contain the blast radius

Investigate and audit

Conclusion

CVE-2026-119618 is a threading bug in httpd's HTTP/2 module, not a flaw in the applications httpd serves. Heap corruption and crashes are public. Code execution is claimed but not yet publicly shown, but that gap is why reachability should drive patch prioritization. Defenders should start with HTTP/2-enabled, public-facing servers.

The timelines are still important to note for security teams. Two teams reported the bug independently, eight days apart. One “team" was an automated, model-driven scanner, while the other was a human team. By November 12, a day after disclosure, a public PoC that corrupts the heap was on GitHub. The window between “advisory published” and “working exploit” is small, and organizations need to be prepared to respond quickly to these notifications.

In this case, the best course of action is to patch first. Until every server is patched and restarted, disable HTTP/2 where you can and use runtime detection to close the gap. A runtime sensor will not see the heap corruption, but it will catch what a successful exploit does next.

原文链接:https://webflow.sysdig.com/blog/httpd-cve-2026-119618-detecting-heap-corruption-and-rce-in-apache-http-server-mod-http2