tsParticles: Malformed JSON requests can terminate the @tsparticles/mcp-server HTTP process
CVE-2026-76892 · GHSA-4p8p-pjpq-2w7h · published 2026-11-09
- Severity
- High
- CVSS score
- 8.7
- Chance of exploitation (EPSS)
- 0.29%
- Fixed in
- 4.3.1
- Exploitation Public proof of concept
- Automatable Yes
- Technical impact Partial
- CISA SSVC
An unauthenticated remote attacker can terminate the exposed MCP process with a single malformed request. The service remains unavailable until restarted by an external supervisor.
Upgrade @tsparticles/mcp-server to 4.3.1 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
Wrap request parsing in a local try/catch and return a bounded HTTP 400 response such as: The process should remain alive after malformed requests.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| @tsparticles/mcp-server | npm | <= 4.3.0 | 4.3.1 |
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- HightsParticles: Unbounded HTTP Request Body Buffering in @tsparticles/mcp-server Leads to Remote DoS@tsparticles/mcp-server
- MediumtsParticles: A single anonymous MCP session can monopolize HTTP mode and deny new clients@tsparticles/mcp-server
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.