Approved changes feed: RSS · Atom

cpe:2.3:a:reactphp:http:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorReactphp (31007f8e-8a30-5abf-afcc-58916a565139)
ProductHttp (7b3f43f8-f68c-51f6-9b30-20d9b3d831b4)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*

Notes

Imported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:github/reactphp/http purl2cpe 2026-06-01 10:11:41.725966

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-104827 vulnerable 2026-11-03 10:16:19.044921 react/http: Unbounded HTTP Client Response Header Buffering Leads to Memory Exhaustion DoS
HIGH (7.5)
react/http is an event-driven, streaming HTTP client and server implementation for ReactPHP. From 1.0.0 until 1.11.1, React\Http\Browser uses ClientRequestStream::handleData() to append response-header bytes to an internal buffer without enforcing a size limit. A remote server can send a valid status line and partial header, withhold the \r\n\r\n or \n\n header terminator, and continue streaming data so the buffer grows for the life of the connection. Applications that fetch attacker-controlled or attacker-influenced URLs, including URLs reached through redirects, can exhaust PHP memory_limit and crash the event-loop or worker process. Confidentiality and integrity are unaffected. This issue is fixed in version 1.11.1.
Published: 2026-10-15T18:19:32.785Z
Updated: 2026-10-16T17:11:59.859Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-84997 vulnerable 2026-10-13 12:28:55.501914 react/http: A malformed HTTP chunked body can lead to a denial-of-service and peg the CPU
HIGH (7.5)
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.
Published: 2026-09-16T14:07:52.948Z
Updated: 2026-09-16T14:46:47.220Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-26044 vulnerable 2026-06-08 05:57:37.911169 ReactPHP's HTTP server continues parsing unused multipart parts after reaching limits
MEDIUM (5.3)
react/http is an event-driven, streaming HTTP client and server implementation for ReactPHP. Previous versions of ReactPHP's HTTP server component contain a potential DoS vulnerability that can cause high CPU load when processing large HTTP request bodies. This vulnerability has little to no impact on the default configuration, but can be exploited when explicitly using the RequestBodyBufferMiddleware with very large settings. This might lead to consuming large amounts of CPU time for processing requests and significantly delay or slow down the processing of legitimate user requests. This issue has been addressed in release 1.9.0. Users are advised to upgrade. Users unable to upgrade may keep the request body limited using RequestBodyBufferMiddleware with a sensible value which should mitigate the issue. An infrastructure or DevOps workaround could be to place a reverse proxy in front of the ReactPHP HTTP server to filter out any excessive HTTP request bodies.
Published: 2023-05-17T17:24:25.855Z
Updated: 2025-01-23T19:52:01.375Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2022-36032 vulnerable 2026-06-08 05:46:06.187558 ReactPHP's HTTP server parses encoded cookie names so malicious `__Host-` and `__Secure-` cookies can be sent
MEDIUM (5.3)
ReactPHP HTTP is a streaming HTTP client and server implementation for ReactPHP. In ReactPHP's HTTP server component versions starting with 0.7.0 and prior to 1.7.0, when ReactPHP is processing incoming HTTP cookie values, the cookie names are url-decoded. This may lead to cookies with prefixes like `__Host-` and `__Secure-` confused with cookies that decode to such prefix, thus leading to an attacker being able to forge cookie which is supposed to be secure. This issue is fixed in ReactPHP HTTP version 1.7.0. As a workaround, Infrastructure or DevOps can place a reverse proxy in front of the ReactPHP HTTP server to filter out any unexpected `Cookie` request headers.
Published: 2022-09-06T18:20:13.000Z
Updated: 2025-04-23T17:14:48.031Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.