Web

CVE-2026-76892

8.7

High

EPSS n/aPatch available

Malformed JSON in MCP POST can crash Node.js process causing service DoS.

exploited

No known exploitation not in CISA KEV as of our last sync

fix

Patch available see the advisory in the references

likelihood

No EPSS score yet

Published 4 Nov 2026Analysed here 5 Nov 2026CVSS scored by the publisher (CNA)

common questions

Is CVE-2026-76892 being exploited?

Not confirmed. CVE-2026-76892 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-76892?

CVE-2026-76892 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-76892?

Yes. A fix has been recorded for CVE-2026-76892. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-76892 affect?

CVE-2026-76892 affects @tsparticles/mcp-server < 4.3.1, tsParticles integrations using MCP HTTP mode, Node.js MCP service instances. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-76892?

Upgrade @tsparticles/mcp-server to v4.3.1+ and add JSON validation/error boundaries.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary

technical analysis

affected

@tsparticles/mcp-server < 4.3.1tsParticles integrations using MCP HTTP modeNode.js MCP service instances

impact

Unauthenticated malformed JSON POST to /mcp triggers a SyntaxError that terminates the Node.js process, causing denial-of-service and service outage.

action required

Immediate action required

affected versions

@tsparticles mcp-server

affected< 4.3.1

tsparticles

affected< 4.3.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

timeline

4 Nov 2026Published
4 Nov 2026CVE record last updated · same day later
5 Nov 2026Analysed by vulneraibility.com · same day later

how to fix

Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.

references

NVD CVE.org CVE Details Source

3 references in the CVE record: 3 links

Linkgithub.com /tsparticles/tsparticles/security/advisories/GHSA-4p8p-pjpq-2w7h
Linkgithub.com /tsparticles/tsparticles/pull/5875
Linkgithub.com /tsparticles/tsparticles/commit/25fb70e7f527a91568adaef576570289083f243b

sources

CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
NVD: CVSS and CPE data
FIRST EPSS: exploit probability and percentile
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free