← Back
CVE-2026-50171
medium
CVSS 6.1
Vulnerability in @angular/common (CVE-2026-50171)
Summary
vulnerability in @angular/common (CVE-2026-50171). Risk of unauthorized operations or information disclosure. Exploitable via ``formatNumber``. Mitigation: upgrade to `21.2.15` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-50171** has been found in @angular/common.
Attackers can target a specific entry point like ``formatNumber`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/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-50171" on the vendor's site.
CVE-2026-50171 (@angular/common) — CWE-400 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `formatNumber` / `DecimalPipe` / `PercentPipe` / `CurrencyPipe`
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-400) exists in @angular/common. Attackers reach the vulnerable code path via ``formatNumber`` without authentication.
📍 Affected scope
@angular/common — . Attack surface: `formatNumber` / `DecimalPipe` / `PercentPipe` / `CurrencyPipe`.
🔥 Severity
Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure
🔧 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"}]}]