tsParticles: A single anonymous MCP session can monopolize HTTP mode and deny new clients
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.3.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 4.3.2.
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Data gap: No advisory context yet
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity6.9/10CVSS 6.9
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
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.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 24/100 · provisional
- Fix
- Fixed in 4.3.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Read the original 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
Upgrade to a fixed version: 4.3.2.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- tsparticles tsparticles
fixed in 4.3.2
- @tsparticles mcp-server
fixed in 4.3.2
Evidence 3
- Advisory
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-76893
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: cve.now feed data
Which versions are affected by CVE-2026-76893?
tsparticles: before 4.3.2. mcp-server: before 4.3.2.Source: cve.now feed data
How do I fix CVE-2026-76893?
Upgrade to a fixed version: 4.3.2.Source: cve.now feed data