@angular/cli 21.2.x and 20.3.x depend on @modelcontextprotocol/sdk@1.31.0 which is vulnerable to CVE-2026-111767, CVE-2026-111768, CVE-2026-111769 and CVE-2026-111771 #34455

Command

other

Is this a regression?

• Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Description

@modelcontextprotocol/sdk versions before 1.32.0 are affected by four advisories published on 2026-10-20, all patched in 1.32.0:

• GHSA-22jm-h49p-29qw (CVE-2026-111767, CVSS 8.6): "MCP TypeScript SDK: Experimental tasks were not tied to the session that created them", affected >= 1.24.0, < 1.32.0
• GHSA-46jr-4wx8-v453 (CVE-2026-111768, CVSS 7.5): "MCP TypeScript SDK: One HTTP request within the default size limit could exhaust server memory during validation", affected >= 1.3.0, < 1.32.0
• GHSA-6prh-2h8m-c8cw (CVE-2026-111769, CVSS 6.5): "MCP TypeScript client SDK: HTTP client transports and OAuth requests followed cross-origin redirects and re-sent custom headers and request bodies", affected < 1.32.0
• GHSA-rvq5-wwqv-78pq (CVE-2026-111771, CVSS 6.8): "MCP TypeScript SDK: Server bearer authentication accepted tokens issued for another service", affected >= 1.6.0, < 1.32.0

Both LTS branches pin a vulnerable version exactly (locked on, no update allowed):

• v21 LTS: @angular/cli 21.2.26 through 21.2.27 (latest) depend on @modelcontextprotocol/sdk@1.31.0 (earlier 21.2.x pinned 1.26.0 and 1.30.0, also affected)
• v20 LTS: @angular/cli 20.3.39 through 20.3.40 (latest) depend on @modelcontextprotocol/sdk@1.31.0 (earlier 20.3.x pinned 1.17.3, 1.24.0, 1.25.2, 1.26.0 and 1.30.0, also affected)

v22 (22.2.x) is not affected: it depends on @modelcontextprotocol/server instead, pinned to the patched 2.3.1 since 22.2.2 (22.2.0 and 22.2.1 pinned 2.0.0, updated in #34266).

The CLI only uses McpServer over stdio, so these do not look reachable through ng mcp, but the exact pin makes npm audit flag every install. npm's advisory feed only has GHSA-22jm-h49p-29qw and GHSA-6prh-2h8m-c8cw so far, so the audit output below lists those two.

The fix would be bumping @modelcontextprotocol/sdk to 1.32.1 (latest, same code as 1.32.0) on both branches, as was done for #34263 (#34264 / #34265).

Minimal Reproduction

1. npm install @angular/cli@21 (or @angular/cli@20)
2. npm audit

Exception or Error

# npm audit report

@modelcontextprotocol/sdk  <=1.31.0
Severity: high
MCP TypeScript SDK: Experimental tasks were not tied to the session that created them - https://github.com/advisories/GHSA-22jm-h49p-29qw
MCP TypeScript client SDK: HTTP client transports and OAuth requests followed cross-origin redirects and re-sent custom headers and request bodies - https://github.com/advisories/GHSA-6prh-2h8m-c8cw
fix available via `npm audit fix --force`
Will install @angular/cli@22.2.3, which is a breaking change
node_modules/@modelcontextprotocol/sdk
  @angular/cli  20.3.13 - 20.3.40 || 21.0.2 - 22.2.0-rc.0
  Depends on vulnerable versions of @modelcontextprotocol/sdk
  node_modules/@angular/cli

Your Environment

Angular CLI       : 21.2.27 / 20.3.40
Package Manager   : npm

Anything else relevant?

No response