Advisory

GHSA-58c5-g7wp-6w37

Also known as: CVE-2025-66035

Summary

Angular is Vulnerable to XSRF Token Leakage via Protocol-Relative URLs in Angular HTTP Client

Details

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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2025-11-26 23:18 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

@angular/common

npm · All systems

Affected

  • introduced 21.0.0-next.0, fixed 21.0.1 (semver)

Fixed versions

21.0.1

Fix

@angular/common

npm · All systems

Affected

  • introduced 20.0.0-next.0, fixed 20.3.14 (semver)

Fixed versions

20.3.14

Fix

@angular/common

npm · All systems

Affected

  • introduced 0, fixed 19.2.16 (semver)

Fixed versions

19.2.16

Fix

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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences