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.
CVE-2026-104827
HIGHPre-NVD 7.57.5Trending — 3 sources updated this week
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-10-15. A secondary CVSS source baseline 7.5; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Also known asEUVD-2026-102255 (ENISA EUVD) · GHSA-g4f2-2pf3-2pwj (GitHub Security Advisories)Source: ENISA EUVD
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5HIGHhigh confidence
- EG Risk
- 49EG Risk 49/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity75% × 45%Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.5% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.5%
- EPSS %ILE
- 44th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 15, 2026
Last Modified
October 16, 2026
Advisory Details (3)
Auto-updated Oct 15, 2026🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available
v1.11.1
Patch available: reactphp/http v1.11.1
https://github.com/reactphp/http/releases/tag/v1.11.1GitHub commit Patch Available
commit 2558622d0b76 (reactphp/http)
Patch available: reactphp/http v1.11.1 (contains commit 2558622d0b76)
https://github.com/reactphp/http/commit/2558622d0b76227c60c61eac8a61572cb6638e8cGitHub advisoryMentions a patch (unverified)🟡 PoC Available
Unbounded HTTP Client Response Header Buffering Leads to Memory Exhaustion DoS in react/http · Advisory · reactphp/http · GitHub
https://github.com/reactphp/http/security/advisories/GHSA-g4f2-2pf3-2pwjVendor Advisories for CVE-2026-104827(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| composer | react/http @ 1.11.1 (fixes >= 1.0.0, <= 1.11.0) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
Packagist(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| react/http | v1.0.0 ... v1.9.0 (12 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 28× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-11-01 08:00 UTCGHSA enrichmentGHSA-g4f2-2pf3-2pwj · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-11-01 08:00 UTCEG score recompute
- 2026-11-01 05:21 UTCEG score recompute
- 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-25 14:55 UTCEG score recompute
- 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-24 12:47 UTCEG score recompute
- 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-18 05:09 UTCEG score recompute
- 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-16 18:30 UTCEG score recompute
- 2026-10-16 17:22 UTCEG score recompute
- 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.4% · 35th percentile
Show 3 moreShow fewer
- 2026-10-15 19:29 UTCEG score recompute
- 2026-10-15 18:24 UTCEG score recomputeFirst assessed: 7.5 HIGH
- 2026-10-15 18:22 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
3 shownPackagist:react/http
Frequently asked(5)
What is CVE-2026-104827?
CVE-2026-104827 is a high-severity vulnerability; its CVE record was published on October 15, 2026. 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…
When was the CVE record for CVE-2026-104827 published?
The CVE record for CVE-2026-104827 was published on October 15, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-104827 actively exploited?
CVE-2026-104827 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-104827?
CVE-2026-104827 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-104827?
A fix for CVE-2026-104827 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-104827 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-104827
Is Your Infrastructure Affected by CVE-2026-104827?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.