GHSA-22jm-h49p-29qw: High severity npm/@modelcontextprotocol/sdk vulnerability

Published Oct 20, 2026
·
Updated

Summary In affected versions, the experimental tasks feature (taskStore) did not check which session created a task. Clients sharing one InMemoryTaskStore could list, read and cancel each other's tasks.

Experimental tasks are deprecated. The 2026-07-28 specification replaced them with a redesigned extension. The best course of action is to stop using them.

Am I affected? Only if your HTTP server passes taskStore to McpServer or Server. If grep -ri taskstore --exclude-dir=nodemodules . finds nothing, you are not affected.

Affected versions: @modelcontextprotocol/sdk 1.24.0 through 1.31.0. The 2.x packages are not affected.

Fix Upgrade to @modelcontextprotocol/sdk 1.32.0 or later. Each task is now tied to the session that created it, so a client that starts a new session can no longer reach its earlier tasks.

If you cannot upgrade yet, remove taskStore, or create one InMemoryTaskStore per session.

Affected Software

1 affected componentFixes available
npm/@modelcontextprotocol/sdk>=1.24.0<1.32.0
1.32.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/@modelcontextprotocol/sdk to a version that resolves this vulnerability.

    Fixed in 1.32.0
  2. Upgrade

    Upgrade @modelcontextprotocol/sdk to a version that resolves this vulnerability.

    Fixed in 1.32.0
  3. Configuration

    If you cannot upgrade, remove taskStore from the HTTP server's McpServer or Server configuration, or create one InMemoryTaskStore per session.

    @modelcontextprotocol/sdk experimental tasks taskStore = disabled or one InMemoryTaskStore per session

Event History

Oct 20, 2026
Advisory Published
via GitHub·06:26 PM
Data Sourced
via GitHub·06:26 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Which deployments are exposed?

Only HTTP servers that pass taskStore to McpServer or Server are affected. Exposure requires clients to share a single InMemoryTaskStore.

2

How can I quickly determine whether our code uses the affected feature?

Run grep -ri taskstore --exclude-dir=node_modules . in the project. If it finds nothing, the deployment is not affected.

3

What can we do if we cannot upgrade immediately?

Remove taskStore, or create a separate InMemoryTaskStore for each session. The recommended longer-term action is to stop using experimental tasks because they are deprecated.

4

What upgrade resolves the issue?

Upgrade @modelcontextprotocol/sdk to version 1.32.0 or later. Versions 1.24.0 through 1.31.0 are affected, while 2.x packages are not affected.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203