Quick answers
- Is CVE-2026-76892 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-76892 being exploited in the wild.
- How severe is CVE-2026-76892?
- High severity, with a CVSS score of 4, published 4 November 2026.
- Which products and versions are affected?
- @tsparticles/mcp-server (npm) <= 4.3.0, SEMVER:introduced=0,fixed=4.3.1; tsParticles @Tsparticles/Mcp-Server prior to 4.3.1.
- Is there a fix for CVE-2026-76892?
- Yes. @tsparticles/mcp-server (npm): upgrade to 4.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-76892 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-76892?
- Check whether you run @tsparticles/mcp-server (npm) or tsParticles @Tsparticles/Mcp-Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @tsparticles/mcp-server (npm): upgrade to 4.3.1 or later
npm install @tsparticles/mcp-server@4.3.1
Technical details
The vulnerability exists in the POST /mcp endpoint of @tsparticles/mcp-server prior to version 4.3.1, where JSON.parse is called outside a proper error boundary, causing an unhandled SyntaxError on malformed input. The attack requires only network access and a malformed JSON body; no authentication or user interaction is needed. A single request terminates the Node.js process, rendering the MCP service unavailable until external restart.
Affected products
- tsparticles @tsparticles/mcp-server prior to 4.3.1
Identifiers
- CVE-2026-76892
- GHSA-4p8p-pjpq-2w7h
Timeline
- 2026-11-04: disclosed
- 2026-07-01: patched