← Back
CVE-2026-50170
high
CVSS 7.5
Vulnerability in @angular/common (CVE-2026-50170)
Summary
vulnerability in @angular/common (CVE-2026-50170). Confidential information can be exposed externally. Exploitable via ``HttpTransferCache``. Mitigation: upgrade to `21.2.15` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-50170** has been found in @angular/common.
Attackers can target a specific entry point like ``HttpTransferCache`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade @angular/common to **21.2.15** or later.
If unsure, ask your IT team or search "@angular/common CVE-2026-50170" on the vendor's site.
CVE-2026-50170 (@angular/common) — CWE-524 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `HttpTransferCache` / `TransferState` / `withCredentials` / `Cookie`
Patched: `21.2.15` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-524) exists in @angular/common. Attackers reach the vulnerable code path via ``HttpTransferCache`` without authentication.
📍 Affected scope
@angular/common — . Attack surface: `HttpTransferCache` / `TransferState` / `withCredentials` / `Cookie`.
🔥 Severity
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to **21.2.15**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r '@angular/common' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@angular/common' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@angular/common` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @angular/common to 21.2.15ステージング環境で 21.2.15 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@angular/common
[{"type":"SEMVER","events":[{"introduced":"21.0.0-next.0"},{"fixed":"21.2.15"}]}]
References
- advisory [email protected]
- package https://github.com/angular/angular
- patch [email protected]
- web https://github.com/advisories/GHSA-q6f4-qqrg-jv6x