@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
I maintainer di solito rispondono entro 1 giorno
Valutazione
- Difficoltà
- 2/5
- Tempo stimato
- 1-3 ore
- Idoneità per principianti
- 35/100
- Tipo di issue
- Bug
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Ferma
- Stack tecnologico
- node.js, typescript
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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:
- https://github.com/advisories/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 - https://github.com/advisories/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 - https://github.com/advisories/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 - https://github.com/advisories/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/cli21.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/cli20.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
- npm install @angular/cli@21 (or @angular/cli@20)
- 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
- Lingua principale
- TypeScript
- Stelle
- 27k
- Fork
- 11.8k
- Merge medio
- 1g 6h
- PR unite (30g)
- 216
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di angular/angular-cli
-
area: @angular/build gemini-triaged
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
angular/angular-cli#33955 ·
I maintainer di solito rispondono entro 1 giorno
-
area: @angular/cli gemini-triaged
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
angular/angular-cli#33055 · 1 commento · 3 reazioni ·
I maintainer di solito rispondono entro 1 giorno
-
@angular/build 22.2.x, 21.2.x and 20.3.x depend on [email protected] / [email protected] which are vulnerable to CVE-2026-112943Forse già presa @florimond-collette l’ha presa oggi. Apertaarea: @angular/build
Difficoltà 3/5 1-2 giorni Idoneità per principianti 25/100
angular/angular-cli#34452 ·
I maintainer di solito rispondono entro 1 giorno
-
`ng generate app-shell` and `ng generate module --route` produce broken imports when a component `type` is configuredForse già presa @MeAkib l’ha presa oggi. Apertaarea: @schematics/angular
Difficoltà 3/5 1-2 giorni Idoneità per principianti 35/100
angular/angular-cli#34449 ·
I maintainer di solito rispondono entro 1 giorno
-
`ng generate component/directive --module` declares a class that doesn't exist when `addTypeToClassName` is `false`Forse già presa @MeAkib l’ha presa oggi. Apertaarea: @schematics/angular
Difficoltà 3/5 1-2 giorni Idoneità per principianti 25/100
angular/angular-cli#34447 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di angular/angular-cli
Issue simili
-
frontend
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 86/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
ranxianglei/billion-context#4172 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
awslabs/threat-composer#362 ·
I maintainer di solito rispondono entro 1 giorno
-
Area/Cloud Needs Triage Type/Bug
Difficoltà 1/5 1-3 ore Idoneità per principianti 86/100
wso2/product-integrator#2847 ·
I maintainer di solito rispondono entro 1 giorno