Skip to main content
VulnerabilityPublished

CVE-2026-76893: tsparticles · Uncontrolled Resource Consumption

Affects tsparticlesSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 4.3.2 when convenient.

Data as of 5 Nov 2026, 00:16 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.06.9
Patch
Available – fixed in 4.3.2
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade tsparticles and mcp-server to 4.3.2.

Affected software

ProductAffectedFixed in
tsparticlestsparticlesAffected
  • <4.3.2
Fixed in
  • 4.3.2
@tsparticlesmcp-serverAffected
  • <4.3.2
Fixed in
  • 4.3.2

AI-suggested

Upgrade to tsparticles version 4.3.2 or later, where this vulnerability is fixed. No other mitigation is required as the issue is resolved in the official patch.

Description

CVE-2026-76893 is a resource consumption vulnerability in the tsparticles TypeScript library prior to version 4.3.2. The issue occurs in the HTTP mode of @tsparticles/mcp-server where a single stateful StreamableHTTPServerTransport instance is shared among all clients. An unauthenticated client can claim this shared transport state by sending an initialization request without an mcp-session-id, causing subsequent clients to be blocked with a 'Server already initialized' error until the server process restarts. The first client's session remains functional. This flaw is fixed in version 4.3.2.

References

Community reviews

Loading reviews…