Sign in Sign up
JA · EN · FR
SecPulse
Categories
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.

Original description

The description as published by the source.

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

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.
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.

📍 Affected scope

Check the vendor advisory for the affected versions of @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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r '@angular/common' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @angular/common を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply 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. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade @angular/common to 19.2.16

    ステージング環境で 19.2.16 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @angular/common
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"19.2.16"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details