Is CVE-2026-63655 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-63655 being exploited in the wild.

How severe is CVE-2026-63655?

High severity, with a CVSS score of 7.5, published 4 November 2026.

Which products and versions are affected?

@tsparticles/mcp-server (npm) < 4.3.1, SEMVER:introduced=0,fixed=4.3.1; tsParticles @Tsparticles/Mcp-Server before 4.3.1.

How is CVE-2026-63655 attacked?

It is attacked over the network.

Am I affected by CVE-2026-63655?

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.

CVE-2026-63655: tsParticles MCP server denial of service via unbounded buffer allocation

Q: Is there a fix for CVE-2026-63655?

Yes. @tsparticles/mcp-server (npm): upgrade to 4.3.1 or later. Until then: Restrict network access to the HTTP server endpoint to trusted sources only, or disable HTTP mode if not required for your integration. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-63655 attacked?

It is attacked over the network.

Q: Am I affected by CVE-2026-63655?

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.

CVE-2026-63655 · Severity: high · CVSS 7.5 · Published 2026-11-04

tsParticles is a TypeScript library for creating particle animations that includes an HTTP server for integration with third-party tools. The MCP server endpoint accepts unauthenticated requests without limiting the size of incoming data, allowing an attacker to stream unlimited data to exhaust server memory and crash the service. The default Docker configuration exposes this endpoint to the internet.

Technologies: @tsparticles/mcp-server (npm), tsParticles @Tsparticles/Mcp-Server. Vendors: npm, tsParticles.

Quick answers

Is CVE-2026-63655 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-63655 being exploited in the wild.
How severe is CVE-2026-63655?: High severity, with a CVSS score of 7.5, published 4 November 2026.
Which products and versions are affected?: @tsparticles/mcp-server (npm) < 4.3.1, SEMVER:introduced=0,fixed=4.3.1; tsParticles @Tsparticles/Mcp-Server before 4.3.1.
Is there a fix for CVE-2026-63655?: Yes. @tsparticles/mcp-server (npm): upgrade to 4.3.1 or later. Until then: Restrict network access to the HTTP server endpoint to trusted sources only, or disable HTTP mode if not required for your integration. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-63655 attacked?: It is attacked over the network.
Am I affected by CVE-2026-63655?: 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
```

Restrict network access to the HTTP server endpoint to trusted sources only, or disable HTTP mode if not required for your integration.

Technical details

The POST /mcp endpoint in @tsparticles/mcp-server prior to 4.3.1 accumulates request body chunks in a Buffer array without enforcing a cumulative size limit, leading to denial of service through memory exhaustion. The vulnerability requires network access but no authentication; any remote attacker can trigger it by streaming an oversized request body. The fix introduces a 1 MB request body size limit and proper rejection of oversized payloads.

Affected products

tsParticles @tsparticles/mcp-server before 4.3.1

Identifiers

CVE-2026-63655
GHSA-447x-qqwf-m7xq

Timeline

2026-11-04: disclosed
2026-11-04: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.