ReactPHP's HTTP server continues parsing unused multipart parts after reaching input field and file upload limits

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

EPSS

• CVE-2023-26044: 0.68% estimated exploitation activity in the next 30 days; percentile 52.43 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Patches The supplied patch resolves this vulnerability for ReactPHP. Workarounds - Keeping the request body limit using RequestBodyBufferMiddleware sensible will mitigate it. - Infrastructure or DevOps can place a reverse proxy in front of the ReactPHP HTTP server to filter out any excessive HTTP request bodies. References A similar vulnerability was discovered in PHP recently, see also PHP's security advisory (CVE-2023-0662). The fix is based on the PHP-FPM fix.

Published by the source

17 May 2023, 17:07 UTC

Last modified by the source

4 Nov 2023, 05:05 UTC

Source last checked

26 Oct 2026, 14:10 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-95x4-j7vc-h8mf

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-26044

Advisory: ReactPHP's HTTP server continues parsing unused multipart parts after reaching input field and file upload limits
IDs: CVE-2023-26044, GHSA-95x4-j7vc-h8mf
Record: https://patchnext.com/advisories/cve-2023-26044 (revision 1, source checked 26 Oct 2026, 14:10 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: react/http 1.9.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist react/http: affected >= 0.8.0, < 1.9.0; fixed in 1.9.0

## Suggested inspection (read-only)
- Packagist react/http: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on react/http.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-95x4-j7vc-h8mf (GitHub-reviewed advisory GHSA-95x4-j7vc-h8mf lists affected ranges: Packagist react/http >=0.8.0 <1.9.0)

Commands are suggestions: review each one before running it.