tsParticles: Malformed JSON requests can terminate the @tsparticles/mcp-server HTTP process
Only the HTTP mode of @tsparticles/mcp-server 4.3.0 and earlier is affected, and the fix is in 4.3.1.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.3.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 4.3.1.
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Data gap: Advisories don't say whether default setups are affected
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
CVE-2026-76892 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects tsparticles and mcp-server; fixed in 4.3.1.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 4.3.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
tsParticles' @tsparticles/mcp-server, when run in HTTP mode, can be crashed by a single malformed JSON request to its POST /mcp endpoint, which can be sent remotely without logging in. The crash takes down the Node.js process, making the MCP service unavailable until something outside the server restarts it.
Read the original description
tsParticles is a TypeScript library for creating highly customizable particle animations. Prior to 4.3.1, the HTTP mode of @tsparticles/mcp-server calls JSON.parse outside a request-local error boundary in the POST /mcp handler in integrations/mcp-server/src/index.ts. A single unauthenticated malformed JSON body raises a SyntaxError that terminates the Node.js process, leaving the MCP service unavailable until an external supervisor restarts it. This issue is fixed in version 4.3.1.
What to do
Upgrade to a fixed version: 4.3.1.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- tsparticles tsparticles
fixed in 4.3.1
- @tsparticles mcp-server
fixed in 4.3.1
Evidence 3
- Advisory
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-76892
Is CVE-2026-76892 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A single malformed JSON request to the /mcp endpoint can terminate the MCP server process, because the request body is parsed outside an error boundary. The service stays unavailable until it is restarted.Source: github.com
Which versions are affected by CVE-2026-76892?
tsparticles: before 4.3.1. mcp-server: before 4.3.1.Source: cve.now feed data
Am I affected, and how do I check?
The condition covers the HTTP mode of @tsparticles/mcp-server version 4.3.0 and earlier. To check a setup, look at the installed @tsparticles/mcp-server version and whether the server is started in HTTP mode.Source: github.com
How do I fix CVE-2026-76892?
Upgrade @tsparticles/mcp-server to version 4.3.1. The advisory says this version appears to fix the issue by returning HTTP 400 for invalid JSON.Source: github.com