webonyx graphql-php is a PHP implementation of the GraphQL specification. Prior to 15.32.3, GraphQL\Language\Parser performs recursive descent without a recursion limit in parseSelectionSet, parseValueLiteral, and parseTypeReference. A remote attacker can submit deeply nested selection sets, object or list values, or list types that exhaust the PHP process stack during pre-validation parsing, before query validation and complexity controls run. The resulting SIGSEGV can terminate PHP-FPM workers or long-running Swoole, RoadRunner, ReactPHP, or CLI processes and cannot be caught by application-level exception handling. This issue is fixed in version 15.32.3.
CVE-2026-107376
HIGHPre-NVD 8.28.2ElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: CISA's SSVC exploitation value: public PoC.EchelonGraph confidence 38%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (39th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Also known asEUVD-2026-95133 (ENISA EUVD)Source: ENISA EUVD
8.2EG
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).
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.2Exploit: No code on recordExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 8.2
- EG Score
- 8.2HIGHmedium confidence
- EG Risk
- 68EG Risk 68/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)Severity82% × 45%Impact severity (EG Severity): CVSS 8.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.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 public PoC (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.4%
- EPSS %ILE
- 39th
- 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 (8.2): severity, escalated by confirmed exploitation. This CVE's 8.2 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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 public PoC (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 8, 2026
Last Modified
October 8, 2026
Advisory Details (4)
Auto-updated Oct 8, 2026Patch available. Sources: github_commit, github_release, github.
GitHub release Patch Available
v15.32.3
Patch available: webonyx/graphql-php v15.32.3
https://github.com/webonyx/graphql-php/releases/tag/v15.32.3GitHub commit Patch Available
commit 7b7f2080ca5f (webonyx/graphql-php)
Patch available: webonyx/graphql-php v15.32.3 (contains commit 7b7f2080ca5f)
https://github.com/webonyx/graphql-php/commit/7b7f2080ca5f7d5340a696fc5701b19a9222d2c2GitHub commit Patch Available
commit 6c1d6009a0f7 (webonyx/graphql-php)
Patch available: webonyx/graphql-php v15.32.3 (contains commit 6c1d6009a0f7)
https://github.com/webonyx/graphql-php/commit/6c1d6009a0f7557f66753bcfd07badd15acf77f4GitHub advisoryMentions a patch (unverified)
Unbounded recursion in parser causes stack overflow on crafted nested input · Advisory · webonyx/graphql-php · GitHub
https://github.com/webonyx/graphql-php/security/advisories/GHSA-r7cg-qjjm-xhqqAffected Packages
(1 across 1 ecosystem)
Packagist(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| webonyx/graphql-php | 14.10.0 ... v15.9.1 (190 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 42× 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-02 16:43 UTCEPSS rescoreEPSS 0.4% · 39th percentile
- 2026-11-01 17:50 UTCEG score recompute
- 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 39th percentile
- 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.4% · 39th percentile
- 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 39th percentile
- 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-10-25 14:54 UTCEG score recompute
- 2026-10-25 06:32 UTCEG score recompute
- 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-10-18 05:07 UTCEG score recompute
- 2026-10-17 19:21 UTCEG score recompute
- 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
Show 17 moreShow fewer
- 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-10-12 16:38 UTCEG score recompute
- 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-10-11 20:14 UTCEG score recompute
- 2026-10-11 18:26 UTCEG score recompute
- 2026-10-11 15:00 UTCEG score recompute
- 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-10-11 04:41 UTCEG score recompute
- 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-10-10 06:40 UTCEG score recompute
- 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-10-08 21:38 UTCEG score recompute
- 2026-10-08 19:18 UTCEG score recompute
- 2026-10-08 18:55 UTCEG score recompute
- 2026-10-08 18:36 UTCEG score recompute
- 2026-10-08 17:54 UTCEG score recomputeFirst assessed: 8.2 HIGH
- 2026-10-08 17:54 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Frequently asked(5)
What is CVE-2026-107376?
CVE-2026-107376 is a high-severity vulnerability; its CVE record was published on October 8, 2026. webonyx graphql-php is a PHP implementation of the GraphQL specification. Prior to 15.32.3, GraphQL\Language\Parser performs recursive descent without a recursion limit in parseSelectionSet, parseValueLiteral, and parseTypeReference. A remote attacker can submit deeply nested selection sets, object…
When was the CVE record for CVE-2026-107376 published?
The CVE record for CVE-2026-107376 was published on October 8, 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 8, 2026; the record at its source may have been updated since.
Is CVE-2026-107376 actively exploited?
CVE-2026-107376 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-107376?
CVE-2026-107376 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-107376?
A fix for CVE-2026-107376 is available: update to the fixed version the vendor names in its advisory.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-107376
Is Your Infrastructure Affected by CVE-2026-107376?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.