← Back
CVE-2025-66035
Vulnerability in @angular/common (CVE-2025-66035)
Summary
vulnerability in @angular/common (CVE-2025-66035). Risk of unauthorized operations or information disclosure. Exploitable via ``POST``. Mitigation: upgrade to `19.2.16` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-66035** has been found in @angular/common.
Attackers can target a specific entry point like ``POST`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade @angular/common to **19.2.16** or later.
If unsure, ask your IT team or search "@angular/common CVE-2025-66035" on the vendor's site.
CVE-2025-66035 (@angular/common) — CWE-201 /
Attack surface: `POST`
Patched: `19.2.16` — apply immediately
Workaround: Developers should avoid using protocol-relative URLs (URLs starting with `//`) in HttpClient requests.
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-201) exists in @angular/common. Attackers reach the vulnerable code path via ``POST`` without authentication.
📍 Affected scope
@angular/common — . Attack surface: `POST`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **19.2.16**.
🛡️ Workaround
Workaround: Developers should avoid using protocol-relative URLs (URLs starting with `//`) in HttpClient requests.
🔍 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 し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Developers should avoid using protocol-relative URLs (URLs starting with `//`) in HttpClient requests.パッチが適用されるまでの応急処置として、Developers should avoid using protocol-relative URLs (URLs starting with `//`) in HttpClient requests. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade @angular/common to 19.2.16ステージング環境で 19.2.16 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、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":"0"},{"fixed":"19.2.16"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-66035
- package https://github.com/angular/angular
- web https://github.com/angular/angular/commit/0276479e7d0e280e0f8d26fa567d3b7aa97a516f
- web https://github.com/angular/angular/commit/05fe6686a97fa0bcd3cf157805b3612033f975bc
- web https://github.com/angular/angular/commit/3240d856d942727372a705252f7c8c115394a41e
- web https://github.com/angular/angular/releases/tag/19.2.16
- web https://github.com/angular/angular/releases/tag/20.3.14
- web https://github.com/angular/angular/releases/tag/21.0.1
- web https://github.com/angular/angular/security/advisories/GHSA-58c5-g7wp-6w37
- web https://cert-portal.siemens.com/productcert/html/ssa-253495.html
- web https://cert-portal.siemens.com/productcert/html/ssa-485750.html
- web https://github.com/advisories/GHSA-58c5-g7wp-6w37