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 類型
缺陷
描述清晰度
描述清楚
活躍度
停滯
技術堆疊
node.js, typescript
領域
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 摘要。