Is react/http 1.8 vulnerable?

Composer · 1 release from 1.8.0 to 1.8.0 · latest react/http is 1.12.0 · checked 18 Nov 2026

Yes: 3 known advisories

Yes. react/http 1.8.0, the last 1.8 release, is affected by 3 known security advisories (2 high, 1 medium), including CVE-2026-104827, CVE-2026-84997, CVE-2023-26044. Upgrade to 1.11.1 or later to fix all of them.

Upgrade with:composer require react/http:^1.11.1

Is your project on an affected react/http?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting react/http 1.8.0

  • HighCVE-2026-104827GHSA-g4f2-2pf3-2pwj15 Oct 2026

    react/http: Unbounded HTTP Client Response Header Buffering Leads to Memory Exhaustion DoS

    Affected
    >=1.0.0 <1.11.1
    Fixed in
    1.11.1
  • HighCVE-2026-84997GHSA-x424-64qh-5j5417 Sept 2026

    react/http: A malformed HTTP chunked body can lead to a denial-of-service and peg the CPU

    Affected
    >=0.6.0 <1.11.1
    Fixed in
    1.11.1
  • MediumCVE-2023-26044GHSA-95x4-j7vc-h8mf17 May 2023

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

    Affected
    >=0.8.0 <1.9.0
    Fixed in
    1.9.0

Which of your client projects are still on react/http 1.8?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact react/http version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other react/http versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.