Is react/http 0.6 vulnerable?

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

Yes: 1 known advisory

Yes. react/http 0.6.0, the last 0.6 release, is affected by 1 known security advisory (1 high), including CVE-2026-84997. 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 0.6.0

  • 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

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

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.