NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2025-66035: Angular is Vulnerable to XSRF Token Leakage via Protocol-Relative URLs in Angular HTTP Client

highCVSS 4.0 7.7GHSA-58c5-g7wp-6w37

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.

Published Nov 26, 2025 · Updated Jun 9, 2026

Affected packages

@angular/common

Ecosystem
npm
Affected
>= 21.0.0-next.0, < 21.0.1
Fixed in
21.0.1
Check
npm ls @angular/common

@angular/common

Ecosystem
npm
Affected
>= 20.0.0-next.0, < 20.3.14
Fixed in
20.3.14
Check
npm ls @angular/common

@angular/common

Ecosystem
npm
Affected
< 19.2.16
Fixed in
19.2.16
Check
npm ls @angular/common

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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

  1. The victim's Angular application must have XSRF protection enabled.
  2. The attacker must be able to make the application send a state-changing HTTP request (e.g., POST) to a protocol-relative URL (e.g., //attacker.com) that they control.

Patches

  • 19.2.16
  • 20.3.14
  • 21.0.1

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.

Credited to alan-agius4, AndrewKushnir, irsl, hybrist, AKiileX.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More npm vulnerabilities

All npm entries