Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

@angular/cli 21.2.x and 20.3.x depend on @modelcontextprotocol/[email protected] which is vulnerable to CVE-2026-111767, CVE-2026-111768, CVE-2026-111769 and CVE-2026-111771

未关闭
#34,455 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@florimond-collette 已经在做这个了。

开始于 2026年10月20日。

  • #34456 来自 @florimond-collette —— 未关闭

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
停滞
领域
devtools, security

调研方向

The issue identifies the exact dependency and affected Angular CLI branches, and links an open pull request (#34456). Read the dependency declarations for the v20 and v21 branches and compare them with the fix described in #34263. Done means the dependency is updated to a patched version on both branches and the reported npm audit vulnerability no longer applies.

由索引模型根据 Issue 内容生成。

描述

area: @angular/cli
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:

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/[email protected] (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/[email protected] (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/[email protected], 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

主要语言
TypeScript
星标
27k
派生
11.8k
平均合并
1 天 6 小时
30 天内合并 PR
216

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

angular/angular-cli 的其他 Issue

查看 angular/angular-cli 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。