CVE-2026-111771: MCP TypeScript SDK: Server bearer authentication accepted tokens issued for another service

Medium CVSS 6.8

OSV id
GHSA-rvq5-wwqv-78pq
Also known as
CVE-2026-111771
Published
Last modified

Affected packages

PackageAffected versionsFixed in
@modelcontextprotocol/sdk
npm
>= 1.6.0, < 1.32.0 1.32.0
@modelcontextprotocol/server
npm
>= 2.0.0, < 2.3.0 2.3.0
@modelcontextprotocol/express
npm
>= 2.0.0, < 2.0.2 2.0.2
@modelcontextprotocol/server-legacy
npm
>= 2.0.0, < 2.3.1 2.3.1

Versions we track that it affects: @modelcontextprotocol/sdk 1.30.0;

How to fix it

@modelcontextprotocol/sdk (npm)

Upgrade @modelcontextprotocol/sdk to 1.32.0 or later.

npm install @modelcontextprotocol/sdk@1.32.0
# if it is an indirect dependency: npm update @modelcontextprotocol/sdk (or npm audit fix)
  • If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

@modelcontextprotocol/server (npm)

Upgrade @modelcontextprotocol/server to 2.3.0 or later.

npm install @modelcontextprotocol/server@2.3.0
# if it is an indirect dependency: npm update @modelcontextprotocol/server (or npm audit fix)
  • If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

@modelcontextprotocol/express (npm)

Upgrade @modelcontextprotocol/express to 2.0.2 or later.

npm install @modelcontextprotocol/express@2.0.2
# if it is an indirect dependency: npm update @modelcontextprotocol/express (or npm audit fix)
  • If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

@modelcontextprotocol/server-legacy (npm)

Upgrade @modelcontextprotocol/server-legacy to 2.3.1 or later.

npm install @modelcontextprotocol/server-legacy@2.3.1
# if it is an indirect dependency: npm update @modelcontextprotocol/server-legacy (or npm audit fix)
  • If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

Not sure whether your project uses an affected version? Check your lockfile below for free.

Details

Summary

In affected versions, the SDK's server-side bearer authentication had no way to check that a token was issued for your server (its audience). Where one authorization server issues tokens for several services, a valid token for another service was also accepted by your MCP server.

Am I affected?

Yes, if your HTTP server uses requireBearerAuth() or verifyBearerToken(), its authorization server also issues tokens for other services, and your verifyAccessToken() does not check the token's audience (aud) itself.

Affected versions:

  • @modelcontextprotocol/sdk 1.6.0 through 1.31.0
  • @modelcontextprotocol/server 2.0.0 through 2.2.0
  • @modelcontextprotocol/express 2.0.0 through 2.0.1
  • @modelcontextprotocol/server-legacy 2.0.0 through 2.3.0
Fix

Upgrade to:

  • 1.x: @modelcontextprotocol/sdk 1.32.0 or later
  • 2.x: @modelcontextprotocol/server 2.3.0 or later, together with @modelcontextprotocol/express 2.0.2 or later if you use it
  • @modelcontextprotocol/server-legacy 2.3.1 or later

Upgrading alone changes nothing. The patched versions add an expectedResource setting that is off by default. To turn the check on, make both of these changes together:

  1. Pass the audience your authorization server puts in tokens for your server: requireBearerAuth({ verifier, expectedResource: new URL('https://mcp.example.com/mcp') }).
  2. Return the token's audience from verifyAccessToken() as AuthInfo.resource, also a URL.

A token for another service then gets 401. With only the first change, every request gets 401.

If you cannot upgrade yet, reject any token whose aud does not include your server inside verifyAccessToken(). That closes the issue on every version.

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.