Is react/http 1.11 vulnerable?

Composer · 2 releases from 1.11.0 to 1.11.1 · latest react/http is 1.12.0 · checked 18 Nov 2026

No known advisories in the last release

react/http 1.11.1, the last 1.11 release, has no known advisories. 2 advisories affect earlier 1.11.x releases, so update to 1.11.1.

Update within 1.11: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

Fixed within 1.11.x, affecting earlier releases

  • 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

Every react/http 1.11.x release

Affected: 1.11.0. 1.11.1 is not affected. Latest react/http: 1.12.0.

VersionKnown advisories
react/http 1.11.1None
react/http 1.11.0CVE-2026-104827, CVE-2026-84997

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

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.