MCP SDK vulnerabilities and security advisories

$ latest 5 · 5 critical, high or exploited

• highFeb 4, 2026

  @modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

  • @modelcontextprotocol/sdk >= 1.10.0, <= 1.25.3 · fixed in 1.26.0
  GHSA-345p-7cg4-v4c7CVE-2026-25536

  prompt for your AI agent

  paste into your agent⧉Copy

  A security advisory covers a package this project may use.
  
  Advisory: GHSA-345p-7cg4-v4c7 (CVE-2026-25536), severity high
  What it is: @modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse
  Affected packages:
  - @modelcontextprotocol/sdk: affected versions >= 1.10.0, <= 1.25.3. Fixed in 1.26.0.
  Details: https://github.com/advisories/GHSA-345p-7cg4-v4c7
  
  Please:
  1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed.
  2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing.
  3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet.
  4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options.
  5. Reinstall, run the build and the tests, and fix anything the upgrade breaks.
  6. Tell me what you changed and which versions are installed now.

• highJan 5, 2026

  Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

  • @modelcontextprotocol/sdk >= 1.3.0, < 1.25.2 · fixed in 1.25.2
  GHSA-8r9q-7v3j-jr4gCVE-2026-0621

  prompt for your AI agent

  paste into your agent⧉Copy

  A security advisory covers a package this project may use.
  
  Advisory: GHSA-8r9q-7v3j-jr4g (CVE-2026-0621), severity high
  What it is: Anthropic's MCP TypeScript SDK has a ReDoS vulnerability
  Affected packages:
  - @modelcontextprotocol/sdk: affected versions >= 1.3.0, < 1.25.2. Fixed in 1.25.2.
  Details: https://github.com/advisories/GHSA-8r9q-7v3j-jr4g
  
  Please:
  1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed.
  2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing.
  3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet.
  4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options.
  5. Reinstall, run the build and the tests, and fix anything the upgrade breaks.
  6. Tell me what you changed and which versions are installed now.

• highDec 2, 2025

  Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

  • @modelcontextprotocol/sdk < 1.24.0 · fixed in 1.24.0
  GHSA-w48q-cv73-mx4wCVE-2025-66414

  prompt for your AI agent

  paste into your agent⧉Copy

  A security advisory covers a package this project may use.
  
  Advisory: GHSA-w48q-cv73-mx4w (CVE-2025-66414), severity high
  What it is: Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default
  Affected packages:
  - @modelcontextprotocol/sdk: affected versions < 1.24.0. Fixed in 1.24.0.
  Details: https://github.com/advisories/GHSA-w48q-cv73-mx4w
  
  Please:
  1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed.
  2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing.
  3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet.
  4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options.
  5. Reinstall, run the build and the tests, and fix anything the upgrade breaks.
  6. Tell me what you changed and which versions are installed now.

• highSep 8, 2025

  MCP Inspector is Vulnerable to Potential Command Execution via XSS When Connecting to an Untrusted MCP Server

  • @modelcontextprotocol/inspector < 0.16.6 · fixed in 0.16.6
  GHSA-g9hg-qhmf-q45mCVE-2025-58444

  prompt for your AI agent

  paste into your agent⧉Copy

  A security advisory covers a package this project may use.
  
  Advisory: GHSA-g9hg-qhmf-q45m (CVE-2025-58444), severity high
  What it is: MCP Inspector is Vulnerable to Potential Command Execution via XSS When Connecting to an Untrusted MCP Server
  Affected packages:
  - @modelcontextprotocol/inspector: affected versions < 0.16.6. Fixed in 0.16.6.
  Details: https://github.com/advisories/GHSA-g9hg-qhmf-q45m
  
  Please:
  1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed.
  2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing.
  3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet.
  4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options.
  5. Reinstall, run the build and the tests, and fix anything the upgrade breaks.
  6. Tell me what you changed and which versions are installed now.

• criticalJun 13, 2025

  MCP Inspector proxy server lacks authentication between the Inspector client and proxy

  • @modelcontextprotocol/inspector < 0.14.1 · fixed in 0.14.1
  GHSA-7f8r-222p-6f5gCVE-2025-49596

  prompt for your AI agent

  paste into your agent⧉Copy

  A security advisory covers a package this project may use.
  
  Advisory: GHSA-7f8r-222p-6f5g (CVE-2025-49596), severity critical
  What it is: MCP Inspector proxy server lacks authentication between the Inspector client and proxy
  Affected packages:
  - @modelcontextprotocol/inspector: affected versions < 0.14.1. Fixed in 0.14.1.
  Details: https://github.com/advisories/GHSA-7f8r-222p-6f5g
  
  Please:
  1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed.
  2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing.
  3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet.
  4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options.
  5. Reinstall, run the build and the tests, and fix anything the upgrade breaks.
  6. Tell me what you changed and which versions are installed now.

From the GitHub Advisory Database, refreshed hourly. Full history on GitHub.