@angular/common
Affected
- introduced
21.0.0-next.0, fixed21.0.1(semver)
Fixed versions
21.0.1
Fix
- Fixed version
21.0.1npm install @angular/[email protected]
Advisory
Also known as: CVE-2025-66035
Angular is Vulnerable to XSRF Token Leakage via Protocol-Relative URLs in Angular HTTP Client
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.
Impact
The token leakage completely bypasses Angular's built-in CSRF protection, allowing an attacker to capture the user's valid XSRF token. Once the token is obtained, the attacker can perform arbitrary Cross-Site Request Forgery (CSRF) attacks against the victim user's session.
Attack Preconditions
POST) to a protocol-relative URL (e.g., //attacker.com) that they control.Patches
Workarounds
Developers should avoid 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.
High Basis: The source's own band: HIGH
21.0.0-next.0, fixed 21.0.1 (semver)21.0.1
21.0.1npm install @angular/[email protected]20.0.0-next.0, fixed 20.3.14 (semver)20.3.14
20.3.14npm install @angular/[email protected]0, fixed 19.2.16 (semver)19.2.16
19.2.16npm install @angular/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0