tsParticles is a TypeScript library for creating highly customizable particle animations. Prior to 4.3.1, the HTTP mode of @tsparticles/mcp-server accepts unauthenticated POST /mcp requests in integrations/mcp-server/src/index.ts and accumulates every request-body chunk in a Buffer[] without a cumulative size limit before Buffer.concat and JSON.parse. A remote attacker can stream an arbitrarily large body to exhaust Node.js process memory and terminate the service, including in the official Docker configuration that exposes HTTP mode on 0.0.0.0:3000. Confidentiality and integrity are not affected. This issue is fixed in version 4.3.1.
CVE-2026-63655
HIGHPre-NVD 7.57.5ElevatedEG-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 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-11-09. 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-117153 (ENISA EUVD) · GHSA-447x-qqwf-m7xq (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).
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5HIGHhigh confidence
- EG Risk
- 65EG Risk 65/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.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
- 37th
- 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.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-09). 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
November 4, 2026
Last Modified
November 6, 2026
Advisory Details (4)
Auto-updated Nov 4, 2026🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_pr.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available
Unbounded HTTP Request Body Buffering in @tsparticles/mcp-server Leads to Remote DoS · Advisory · tsparticles/tsparticles · GitHub
https://github.com/tsparticles/tsparticles/security/advisories/GHSA-447x-qqwf-m7xqGitHub pull request
4.3.1
Fix merged in tsparticles/tsparticles PR #5875 on 2026-07-01 — awaiting tagged release
https://github.com/tsparticles/tsparticles/pull/5875GitHub commit
commit 7b3a9488d420 (tsparticles/tsparticles)
Fix landed in tsparticles/tsparticles commit 7b3a9488d420 — awaiting tagged release
https://github.com/tsparticles/tsparticles/commit/7b3a9488d4201fe9ddd5fec05f4a2ae65d3627eaGitHub commit
commit 25fb70e7f527 (tsparticles/tsparticles)
Fix landed in tsparticles/tsparticles commit 25fb70e7f527 — awaiting tagged release
https://github.com/tsparticles/tsparticles/commit/25fb70e7f527a91568adaef576570289083f243bVendor Advisories for CVE-2026-63655(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 |
|---|---|---|---|
| npm | @tsparticles/mcp-server @ 4.3.1 (fixes < 4.3.1) | — | 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)
npm(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| @tsparticles/mcp-server | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 12× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-13 16:53 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-11-09 21:46 UTCEchelonGraph re-scored
- 2026-11-09 21:46 UTCGHSA enrichmentGHSA-447x-qqwf-m7xq · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-11-06 21:47 UTCEchelonGraph re-scored
- 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-11-05 21:26 UTCEchelonGraph re-scored
- 2026-11-05 20:27 UTCEchelonGraph re-scored
- 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-11-04 23:03 UTCENISA EUVD ID recordedEUVD-2026-117153 · Source: ENISA EUVD
- 2026-11-04 22:27 UTCEchelonGraph re-scored
- 2026-11-04 22:17 UTCEchelonGraph re-scoredFirst assessed: 7.5 HIGH
- 2026-11-04 22:15 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Frequently asked(5)
What is CVE-2026-63655?
CVE-2026-63655 is a high-severity vulnerability; its CVE record was published on November 4, 2026. tsParticles is a TypeScript library for creating highly customizable particle animations. Prior to 4.3.1, the HTTP mode of @tsparticles/mcp-server accepts unauthenticated POST /mcp requests in integrations/mcp-server/src/index.ts and accumulates every request-body chunk in a Buffer[] without a…
When was the CVE record for CVE-2026-63655 published?
The CVE record for CVE-2026-63655 was published on November 4, 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 November 6, 2026; the record at its source may have been updated since.
Is CVE-2026-63655 actively exploited?
CVE-2026-63655 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-63655?
CVE-2026-63655 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-63655?
A fix for CVE-2026-63655 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-63655 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-63655
Is Your Infrastructure Affected by CVE-2026-63655?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.