npmWorst: High2 advisories

@modelcontextprotocol/client: known vulnerabilities

@modelcontextprotocol/client has 2 reviewed security advisories in the GitHub Advisory Database — 1 high, 1 moderate. The most recent was published 2026-10-20. Each one below lists the affected version range, the release that fixes it, its CVE and severity. SkyShield matches these against the @modelcontextprotocol/client versions running across your servers, containers and images, and ranks what to patch first.

How to fix @modelcontextprotocol/client

Upgrade @modelcontextprotocol/client to a release at or above the fixed version shown for each advisory below. For npm:

npm install @modelcontextprotocol/client@2.3.0 (or run npm audit fix)

SkyShield checks the installed version on every machine and container, so you can see which hosts are still on an affected release after you roll the fix out.

Advisories (2)

MCP TypeScript client SDK: HTTP client transports and OAuth requests followed cross-origin redirects and re-sent custom headers and request bodies Moderate 6.5 CWE-200 — Affected: from 2.0.0 up to 2.3.0. Fixed in 2.3.0. Published 2026-10-20. GHSA-6prh-2h8m-c8cw · CVE-2026-111769
MCP TypeScript SDK: OAuth client could send credentials to an authorization server chosen by the MCP server High 7.5 CWE-345 CWE-522 — Affected: from 2.0.0 up to 2.2.0. Fixed in 2.2.0. Published 2026-10-06. GHSA-6qxp-vccf-f47h · CVE-2026-104850

Find @modelcontextprotocol/client across your fleet

Install one agent per server and connect your cloud. SkyShield matches your packages and images against GHSA, CISA KEV and EPSS and shows the fix per machine. Free for one server, then from $49 per server a month. Start free.