CVE-2026-84997: react/http A Malformed HTTP Chunked Body Vulnerability

HIGH
Advisory Identifier: GHSA-x424-64qh-5j54
CVSS 7.5
CWE-835
Published
Advisory Summary

CVE-2026-84997 is a HIGH (CVSS 7.5) a malformed http chunked body vulnerability (CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop')) affecting react/http libraries in the Packagist ecosystem. The issue involves a malformed http chunked body can lead to a denial-of-service and peg the cpu. Remediation is available by upgrading affected packages to version 1.11.1.

CVE-2026-84997 at a Glance

CVE Identifier CVE-2026-84997
GHSA Identifier GHSA-x424-64qh-5j54
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop')
Affected Product react/http
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-84997

To remediate this vulnerability, upgrade all affected react/http dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

react/http fixed: 1.11.1
Upgrade react/http to 1.11.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for react/http

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-84997, inspect your project dependencies for react/http:

inspect dependencies for react/http

Analyze the terminal output to locate any version of react/http in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.11.1), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop'), where the product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop. In react/http, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary A malformed HTTP message using `Transfer-Encoding: chunked` can drive `React\Http\Io\ChunkedDecoder` into an infinite loop, pegging a CPU core and freezing the event loop. Because ReactPHP is single-threaded, one such message stalls the entire process for every client until it is killed. Both directions are affected. `ChunkedDecoder` decodes chunked **request** bodies for `React\Http\HttpServer` and chunked **response** bodies for `React\Http\Browser`, so a server can be attacked by a malicious client and a client can be attacked by a malicious or compromised server. ### Details `ChunkedDecoder::handleData()` loops `while ($this->buffer !== '')` and relies on the buffer shrinking each iteration. Two states leave the buffer unchanged while the loop condition stays true. **Terminal-chunk trailer.** After the terminating `0` chunk, any remaining buffer is treated as trailer data to skip: ```php } elseif ($this->chunkSize === 0) { $this->buffer = (string)\substr($this->buffer, $positionCrlf); } ``` When the trailer holds no CRLF yet, `strpos()` returns `false`, PHP coerces that to `0` in `substr()`, and the buffer is never advanced. Neither the error guard (which requires a non-zero chunk size) nor the wait guard (which requires fewer than two bytes remaining) can fire, so the loop re-enters with identical state. **Off-by-one after a completed chunk.** Once a non-terminal chunk has been fully transferred, the "chunk does not end with a CRLF" error guard requires `strlen($this->buffer) > 2` while the wait guard requires `< 2`. Exactly two non-CRLF bytes slip past both, and because the chunk is already complete nothing is consumed on the next iteration. ### PoC Run the example server from the `reactphp/reactphp` README and send a malformed request. Note the missing trailing `\r\n`: ``` POST / HTTP/1.1\r\nHost: x\r\nTransfer-Encoding: chunked\r\n\r\n0\r\nab ``` The PHP process pegs at 100% CPU and stops answering legitimate requests. A body of `1\r\nAAB` triggers the second state. The client side is reachable the same way: a `Browser` request to a server that answers with `Transfer-Encoding: chunked` and either malformed body shape hangs the client process. ### Impact Denial of service. The affected process stops responding entirely and has to be killed. Servers behind a reverse proxy that parses and re-frames HTTP, such as a typical nginx setup, are not affected on the **server** side, because the proxy normalises the request before it reaches PHP. That mitigation does not extend to the **client** side: outbound requests made with `Browser` reach the remote server directly, so an application fetching attacker-influenced URLs is affected regardless of what sits in front of it.

CVE-2026-84997 Affected react/http Versions

1 component(s)
Fixed Versions:
1.11.1
Product / Package Ecosystem Affected Versions Fixed Version
react/http
Packagist
≥ 0.6.0
< 1.11.1
1.11.1

References

Frequently Asked Questions

What is CVE-2026-84997?
CVE-2026-84997 is a security vulnerability in react/http involving A malformed HTTP chunked body can lead to a denial-of-service and peg the CPU under CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop').
Which react/http versions are affected?
Affected versions include releases prior to 1.11.1 across affected packages: react/http.
What version fixes CVE-2026-84997?
Upgrading to 1.11.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is react/http affected?
Yes, react/http is affected in releases prior to 1.11.1. Upgrade your dependency to 1.11.1 or later.
What is the CVSS score of CVE-2026-84997?
CVE-2026-84997 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-84997?
CVE-2026-84997 is classified under CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') (The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.).
How can I check Packagist dependencies for CVE-2026-84997?
Run the dependency tree command: 'inspect dependencies for react/http'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-x424-64qh-5j54",
  "modified" : "2026-09-17T20:32:39Z",
  "published" : "2026-09-17T20:32:39Z",
  "aliases" : [ "CVE-2026-84997" ],
  "summary" : "react/http: A malformed HTTP chunked body can lead to a denial-of-service and peg the CPU",
  "details" : "### Summary\n\nA malformed HTTP message using `Transfer-Encoding: chunked` can drive `React\\Http\\Io\\ChunkedDecoder` into an infinite loop, pegging a CPU core and freezing the event loop. Because ReactPHP is single-threaded, one such message stalls the entire process for every client until it is killed.\n\nBoth directions are affected. `ChunkedDecoder` decodes chunked **request** bodies for `React\\Http\\HttpServer` and chunked **response** bodies for `React\\Http\\Browser`, so a server can be attacked by a malicious client and a client can be attacked by a malicious or compromised server.\n\n### Details\n\n`ChunkedDecoder::handleData()` loops `while ($this->buffer !== '')` and relies on the buffer shrinking each iteration. Two states leave the buffer unchanged while the loop condition stays true.\n\n**Terminal-chunk trailer.** After the terminating `0` chunk, any remaining buffer is treated as trailer data to skip:\n\n```php\n} elseif ($this->chunkSize === 0) {\n    $this->buffer = (string)\\substr($this->buffer, $positionCrlf);\n}\n```\n\nWhen the trailer holds no CRLF yet, `strpos()` returns `false`, PHP coerces that to `0` in `substr()`, and the buffer is never advanced. Neither the error guard (which requires a non-zero chunk size) nor the wait guard (which requires fewer than two bytes remaining) can fire, so the loop re-enters with identical state.\n\n**Off-by-one after a completed chunk.** Once a non-terminal chunk has been fully transferred, the \"chunk does not end with a CRLF\" error guard requires `strlen($this->buffer) > 2` while the wait guard requires `< 2`. Exactly two non-CRLF bytes slip past both, and because the chunk is already complete nothing is consumed on the next iteration.\n\n### PoC\n\nRun the example server from the `reactphp/reactphp` README and send a malformed request. Note the missing trailing `\\r\\n`:\n\n```\nPOST / HTTP/1.1\\r\\nHost: x\\r\\nTransfer-Encoding: chunked\\r\\n\\r\\n0\\r\\nab\n```\n\nThe PHP process pegs at 100% CPU and stops answering legitimate requests. A body of `1\\r\\nAAB` triggers the second state.\n\nThe client side is reachable the same way: a `Browser` request to a server that answers with `Transfer-Encoding: chunked` and either malformed body shape hangs the client process.\n\n### Impact\n\nDenial of service. The affected process stops responding entirely and has to be killed.\n\nServers behind a reverse proxy that parses and re-frames HTTP, such as a typical nginx setup, are not affected on the **server** side, because the proxy normalises the request before it reaches PHP. That mitigation does not extend to the **client** side: outbound requests made with `Browser` reach the remote server directly, so an application fetching attacker-influenced URLs is affected regardless of what sits in front of it.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "react/http"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.6.0"
      }, {
        "fixed" : "1.11.1"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.11.0"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/reactphp/http/security/advisories/GHSA-x424-64qh-5j54"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-84997"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/reactphp/http/commit/b6d4688790adf3797071fcf88a3fc4225f30486a"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/FriendsOfPHP/security-advisories/blob/master/react/http/CVE-2026-84997.yaml"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/reactphp/http"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/reactphp/http/releases/tag/v1.11.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-835" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-17T20:32:39Z",
    "nvd_published_at" : "2026-09-16T15:18:00Z"
  }
}