Skip to main content
VulnerabilityPublished

CVE-2026-84997: reactphp http · Infinite Loop

Affects reactphp httpSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 1.11.1 soon.

Data as of 30 Oct 2026, 20:25 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.11.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade http and reactphp/http to 1.11.1.

Affected software

ProductAffectedFixed in
reactphphttpAffected
  • >=0.6.0 <1.11.1
Fixed in
  • 1.11.1
GitHubreactphp/httppkg:github/reactphp/httpOther threatsAffected
  • >=0.6.0 <1.11.1
Fixed in
  • 1.11.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade reactphp http to version 1.11.1 or later, where this infinite loop issue is fixed. If upgrading is not immediately possible, consider using a reverse proxy that normalizes inbound requests to protect the server side, though this does not mitigate the client-side risk. Patch status is confirmed fixed in version 1.11.1.

Description

react/http is an event-driven, streaming HTTP client and server implementation for ReactPHP. From 0.6.0 until 1.11.1, React\Http\Io\ChunkedDecoder could enter an infinite loop while processing a malformed Transfer-Encoding: chunked body because handleData required its buffer to shrink on every iteration. An incomplete terminal-chunk trailer without CRLF left the buffer unchanged after strpos returned false, and exactly two non-CRLF bytes after a completed non-terminal chunk bypassed both the error and wait guards. The affected decoder processes request bodies for React\Http\HttpServer and response bodies for React\Http\Browser, allowing a malicious client to freeze a server or a malicious or compromised server to freeze a client. A reverse proxy that normalizes inbound requests may protect the server direction but does not protect outbound Browser requests. This issue is fixed in version 1.11.1.

References

Community reviews

Loading reviews…