React/Http (1.0.0-1.11.0) - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/react/http-1.0.0-1.11.0/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioThu, 15 Oct 2026 22:27:19 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgUnbounded HTTP Response Header Buffering in react/httphttps://feed.craftedsignal.io/briefs/2026-10-react-http-dos/Thu, 15 Oct 2026 22:27:19 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-10-react-http-dos/The react/http library is vulnerable to a memory exhaustion Denial of Service (DoS) due to the lack of size constraints on incoming HTTP response headers (CVE-2026-104827).The react/http library, specifically within the ClientRequestStream component, fails to impose a size limit on incoming HTTP response headers. The handleData() method appends every incoming byte directly to an internal buffer without checking length, searching only for the \r\n\r\n or \n\n header terminator. An attacker hosting a malicious HTTP endpoint can stream an arbitrary amount of data to a client using the library, withholding the terminator and causing the client's memory consumption to grow monotonically until the PHP memory_limit is reached. This results in the crashing of the process or the entire event loop. The vulnerability affects all versions of react/http from 1.0.0 through 1.11.0. This issue is remotely exploitable without authentication, including cases where a client is directed to a malicious URL via an HTTP redirect, making it a significant risk for applications that perform arbitrary external requests.

Impact

The vulnerability allows for a remotely triggerable, unauthenticated denial of service against any application that uses the react/http Browser class to fetch data from untrusted sources. Successful exploitation causes the application process to crash due to memory exhaustion, leading to a loss of service availability for the affected process or worker. No confidentiality or integrity impact occurs, but the service disruption is total for the victim process.

Recommendation

  • Upgrade the react/http package to a version beyond 1.11.0 that implements the necessary header size constraints.
  • Audit applications utilizing react/http to identify endpoints that perform outbound requests to potentially untrusted or attacker-controlled domains.
  • Implement egress filtering or network-level timeouts for outbound requests to mitigate the impact of long-lived, slow-header-streaming connections.
  • Deploy the patches for CVE-2026-104827 across all environments where react/http is used as a client-side component.
]]>lowadvisory