CVE-2026-104827: react/http Denial of Service Vulnerability

HIGH
Advisory Identifier: GHSA-g4f2-2pf3-2pwj
CVSS 7.5
CWE-770
Published
Advisory Summary

CVE-2026-104827 is a HIGH (CVSS 7.5) denial of service vulnerability (CWE-770: Allocation of Resources Without Limits or Throttling) affecting react/http libraries in the Packagist ecosystem. The issue involves unbounded http client response header buffering leads to memory exhaustion dos. Remediation is available by upgrading affected packages to version 1.11.1.

CVE-2026-104827 at a Glance

CVE Identifier CVE-2026-104827
GHSA Identifier GHSA-g4f2-2pf3-2pwj
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-770: Allocation of Resources Without Limits or Throttling
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-104827

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-104827, 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-770: Allocation of Resources Without Limits or Throttling, where the product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. 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 `React\Http\Browser` and its lower-level HTTP stack impose no limit on the size of a response's header section while it is being received. `ClientRequestStream::handleData()` appends every incoming byte to an internal buffer and only scans that buffer for the `\r\n\r\n` (or `\n\n`) terminator, without ever checking its length. A remote server that withholds the terminator and keeps streaming can grow the client's memory without bound until PHP's `memory_limit` is exhausted and the process crashes. This is an unauthenticated, network-reachable denial of service against any application that uses `react/http` as a client to fetch untrusted or attacker-influenced URLs, including via redirects. ### Details `ClientRequestStream::handleData()` is bound directly to the underlying connection's `data` event, so every byte the peer sends is appended with no size check: ```php public function handleData($data) { $this->buffer .= $data; // buffer until double CRLF (or double LF for compatibility with legacy servers) $eom = \strpos($this->buffer, "\r\n\r\n"); $eomLegacy = \strpos($this->buffer, "\n\n"); if ($eom !== false || $eomLegacy !== false) { ``` The only exit from the buffering state is finding the header terminator or a connection close, so until it arrives the buffer grows monotonically for as long as the peer keeps sending. The codebase already applies this class of limit elsewhere, but not symmetrically. `RequestHeaderParser` caps incoming **request** headers when acting as a server, and `Transaction::bufferResponse()` caps the response **body**, but only once the header section has already been parsed into a `Response`. Response header reception was the one stage with no limit at all. ### PoC An HTTP server that sends a valid status line and a partial header, then streams indefinitely without ever terminating the header section: ```bash php -r '$s=stream_socket_server("tcp://127.0.0.1:18080"); $c=stream_socket_accept($s); fread($c,8192); fwrite($c,"HTTP/1.1 200 OK\r\nX-Fill: "); while (true) { fwrite($c, str_repeat("A",1048576)); usleep(10000); }' ``` A client fetching it, with `memory_limit=64M`: ```php $browser = new React\Http\Browser(); $browser->get("http://127.0.0.1:18080/")->then( function () { echo "ok\n"; }, function ($e) { echo get_class($e) . ": " . $e->getMessage() . "\n"; } ); ``` Client memory grows steadily until the process dies with `Allowed memory size ... exhausted` inside `ClientRequestStream::handleData()`. ### Impact Remotely triggerable, unauthenticated denial of service against any process using `Browser` to fetch from an attacker-controlled, compromised or otherwise untrusted endpoint, including one reached through a redirect. No user interaction and no special privileges are required. Because there is no upper bound on the header buffer, a single cheap connection can drive memory arbitrarily high and crash the process, taking down whatever event loop or worker it was running. Confidentiality and integrity are unaffected; availability is fully impacted for that process.

CVE-2026-104827 Affected react/http Versions

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

References

Frequently Asked Questions

What is CVE-2026-104827?
CVE-2026-104827 is a security vulnerability in react/http involving Unbounded HTTP Client Response Header Buffering Leads to Memory Exhaustion DoS under CWE-770: Allocation of Resources Without Limits or Throttling.
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-104827?
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-104827?
CVE-2026-104827 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-104827?
CVE-2026-104827 is classified under CWE-770: Allocation of Resources Without Limits or Throttling (The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.).
How can I check Packagist dependencies for CVE-2026-104827?
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-g4f2-2pf3-2pwj",
  "modified" : "2026-10-15T20:09:56Z",
  "published" : "2026-10-15T20:09:56Z",
  "aliases" : [ "CVE-2026-104827" ],
  "summary" : "react/http: Unbounded HTTP Client Response Header Buffering Leads to Memory Exhaustion DoS",
  "details" : "### Summary\n\n`React\\Http\\Browser` and its lower-level HTTP stack impose no limit on the size of a response's header section while it is being received. `ClientRequestStream::handleData()` appends every incoming byte to an internal buffer and only scans that buffer for the `\\r\\n\\r\\n` (or `\\n\\n`) terminator, without ever checking its length. A remote server that withholds the terminator and keeps streaming can grow the client's memory without bound until PHP's `memory_limit` is exhausted and the process crashes.\n\nThis is an unauthenticated, network-reachable denial of service against any application that uses `react/http` as a client to fetch untrusted or attacker-influenced URLs, including via redirects.\n\n### Details\n\n`ClientRequestStream::handleData()` is bound directly to the underlying connection's `data` event, so every byte the peer sends is appended with no size check:\n\n```php\npublic function handleData($data)\n{\n    $this->buffer .= $data;\n\n    // buffer until double CRLF (or double LF for compatibility with legacy servers)\n    $eom = \\strpos($this->buffer, \"\\r\\n\\r\\n\");\n    $eomLegacy = \\strpos($this->buffer, \"\\n\\n\");\n    if ($eom !== false || $eomLegacy !== false) {\n```\n\nThe only exit from the buffering state is finding the header terminator or a connection close, so until it arrives the buffer grows monotonically for as long as the peer keeps sending.\n\nThe codebase already applies this class of limit elsewhere, but not symmetrically. `RequestHeaderParser` caps incoming **request** headers when acting as a server, and `Transaction::bufferResponse()` caps the response **body**, but only once the header section has already been parsed into a `Response`. Response header reception was the one stage with no limit at all.\n\n### PoC\n\nAn HTTP server that sends a valid status line and a partial header, then streams indefinitely without ever terminating the header section:\n\n```bash\nphp -r '$s=stream_socket_server(\"tcp://127.0.0.1:18080\"); $c=stream_socket_accept($s); fread($c,8192); fwrite($c,\"HTTP/1.1 200 OK\\r\\nX-Fill: \"); while (true) { fwrite($c, str_repeat(\"A\",1048576)); usleep(10000); }'\n```\n\nA client fetching it, with `memory_limit=64M`:\n\n```php\n$browser = new React\\Http\\Browser();\n$browser->get(\"http://127.0.0.1:18080/\")->then(\n    function () { echo \"ok\\n\"; },\n    function ($e) { echo get_class($e) . \": \" . $e->getMessage() . \"\\n\"; }\n);\n```\n\nClient memory grows steadily until the process dies with `Allowed memory size ... exhausted` inside `ClientRequestStream::handleData()`.\n\n### Impact\n\nRemotely triggerable, unauthenticated denial of service against any process using `Browser` to fetch from an attacker-controlled, compromised or otherwise untrusted endpoint, including one reached through a redirect. No user interaction and no special privileges are required. Because there is no upper bound on the header buffer, a single cheap connection can drive memory arbitrarily high and crash the process, taking down whatever event loop or worker it was running. Confidentiality and integrity are unaffected; availability is fully impacted for that process.",
  "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" : "1.0.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-g4f2-2pf3-2pwj"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/reactphp/http/commit/2558622d0b76227c60c61eac8a61572cb6638e8c"
  }, {
    "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-770" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-10-15T20:09:56Z",
    "nvd_published_at" : null
  }
}