NewApp Monitoring is liveSign up free
AgentbeamBeta
AI agent vulnerability · Other MCP servers and tools

CVE-2026-76892: tsParticles: Malformed JSON requests can terminate the @tsparticles/mcp-server HTTP process

highCVSS 4.0 8.7GHSA-4p8p-pjpq-2w7h

The HTTP mode of the npm package @tsparticles/mcp-server, in versions up to 4.3.0, crashes on a single malformed JSON request to /mcp. An unauthenticated remote attacker can kill the Node.js process and keep the service down until something restarts it. Upgrade to 4.3.1.

Published Nov 9, 2026 · Analysis Nov 9, 2026

What an attacker can do

The /mcp POST handler in integrations/mcp-server/src/index.ts reads the request body and calls JSON.parse() on it with no try/catch. When the body is not valid JSON, the call throws inside an async handler. Nothing catches the error, so the whole Node.js process exits with code 1.

The reporter reproduced it three times out of three on v4.3.0 with a truncated body, {"jsonrpc":, which produced SyntaxError: Unexpected end of JSON input at index.ts line 407. No credentials are needed and no user interaction. The result is availability loss only: the MCP server stays down until a supervisor such as systemd, Docker or PM2 starts it again, and an attacker can repeat the request after each restart. Teams that expose this server to a network, or let AI agents rely on it for tooling, lose that tool each time. The advisory reports no data exposure.

Who is affected

@tsparticles/mcp-server version 4.3.0 and earlier is affected, but only when it runs in HTTP mode and serves /mcp. The stdio mode does not take this request path. Check the installed version:

npm ls @tsparticles/mcp-server

If you run it through npx or a container image, check the pinned tag. Also check whether the HTTP port is reachable from untrusted networks.

@tsparticles/mcp-server

Ecosystem
npm
Affected
<= 4.3.0
Fixed in
4.3.1
Check
npm ls @tsparticles/mcp-server

How to fix it

Upgrade to 4.3.1:

npm install @tsparticles/[email protected]

The fix is commit 25fb70e7f527a91568adaef576570289083f243b. It moves JSON.parse into its own try block and returns HTTP 400 with an Invalid JSON error for bad input. The same change returns HTTP 413 when the body exceeds MAX_REQUEST_BODY_BYTES (the related pull request mentions a 1 MB limit). The process now stays alive after a malformed request. The sources list no workaround. As a general precaution that is not from the advisory, keep the HTTP port off untrusted networks and run the process under a supervisor.

How to tell if you were hit

Look for the process exiting with code 1 and a stack trace that begins with SyntaxError: Unexpected end of JSON input (or another JSON SyntaxError) at integrations/mcp-server/src/index.ts. Repeated restarts of the service in your supervisor logs point to the attack. Check access logs or proxy logs for POST /mcp requests with truncated or non-JSON bodies, and note the source addresses.

Original advisory

From the GitHub Advisory Database (CC BY 4.0).

Summary

The HTTP mode of @tsparticles/mcp-server parses incoming /mcp request bodies with JSON.parse() outside a request-local error boundary. A single malformed JSON request causes the async request handler to throw and terminates the Node.js process.

This was verified on v4.3.0 at commit 0266d469aa2d719cb66a9c6bf09aded4186ec17c. Version 4.3.1 appears to fix this by returning HTTP 400 for invalid JSON.

Affected Code

The vulnerable handler is:

if (req.method === "POST" && req.url === "/mcp") { const body = await new Promise((resolve, reject) => { const chunks: Buffer[] = []; req.on("data", (chunk) => chunks.push(Buffer.from(chunk))); req.on("end", () => resolve(Buffer.concat(chunks).toString("utf8"))); req.on("error", reject); });

const parsedBody = body ? JSON.parse(body) : undefined; await transport.handleRequest(req, res, parsedBody); }

The JSON.parse() call is not wrapped in try/catch.

Reproduction

Start the HTTP server and send this malformed request:

POST /mcp HTTP/1.1 Content-Type: application/json Mcp-Protocol-Version: 2025-11-25

{"jsonrpc":

Observed result in 3 out of 3 runs:

exit_code=1 SyntaxError: Unexpected end of JSON input at Server. (integrations/mcp-server/src/index.ts:407:38)

Impact

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.

Recommendation

Wrap request parsing in a local try/catch and return a bounded HTTP 400 response such as:

{"error":"Invalid JSON"}

The process should remain alive after malformed requests.

Credited to NetKingJ.

Questions

Is @tsparticles/mcp-server 4.3.0 affected by CVE-2026-76892?

Yes. Versions up to and including 4.3.0 are affected in HTTP mode. Version 4.3.1 is the patched release.

Does the attacker need to log in?

No. The advisory describes an unauthenticated remote attacker who sends one malformed request to /mcp.

Can this leak data or run code?

No source says so. The impact is a crash of the Node.js process, a denial of service, until a supervisor restarts it.

Is it exploited in the wild?

No source we read reports exploitation, and the entry has no CISA KEV record.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology

More Other MCP servers and tools vulnerabilities

All Other MCP servers and tools entries