CVE-2025-66035: @angular/common Angular Is Vulnerable To XSRF Vulnerability

HIGH
Advisory Identifier: GHSA-58c5-g7wp-6w37
CWE-359 CWE-201
Published
Advisory Summary

CVE-2025-66035 is a HIGH angular is vulnerable to xsrf vulnerability (CWE-359: Exposure of Private Personal Information to an Unauthorized Actor) affecting @angular/common libraries in the npm ecosystem. The issue involves angular is vulnerable to xsrf token leakage via protocol-relative urls in angular http client. Remediation is available by upgrading affected packages to version 21.0.1, 20.3.14, 19.2.16.

CVE-2025-66035 at a Glance

CVE Identifier CVE-2025-66035
GHSA Identifier GHSA-58c5-g7wp-6w37
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-359: Exposure of Private Personal Information to an Unauthorized Actor
Affected Product @angular/common
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2025-66035

To remediate this vulnerability, upgrade all affected @angular/common dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@angular/common fixed: 21.0.1
npm install @angular/common@21.0.1
@angular/common fixed: 20.3.14
npm install @angular/common@20.3.14
@angular/common fixed: 19.2.16
npm install @angular/common@19.2.16
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls @angular/common

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2025-66035, inspect your project dependencies using npm:

npm ls @angular/common

Analyze the terminal output to locate any version of @angular/common in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 21.0.1), your application is affected.

Note: The npm ls @angular/common command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-359: Exposure of Private Personal Information to an Unauthorized Actor, where the product does not properly prevent a person's private, personal information from being accessed by actors who either (1) are not explicitly authorized to access the information or (2) do not have the implicit consent of the person about whom the information is collected. In @angular/common, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

CVE-2025-66035 Affected @angular/common Versions

3 component(s)
Fixed Versions:
21.0.120.3.1419.2.16
Product / Package Ecosystem Affected Versions Fixed Version
@angular/common
npm
≥ 21.0.0-next.0
< 21.0.1
21.0.1
@angular/common
npm
≥ 20.0.0-next.0
< 20.3.14
20.3.14
@angular/common
npm
< 19.2.16
19.2.16

References

Frequently Asked Questions

What is CVE-2025-66035?
CVE-2025-66035 is a security vulnerability in @angular/common involving Angular is Vulnerable to XSRF Token Leakage via Protocol-Relative URLs in Angular HTTP Client under CWE-359: Exposure of Private Personal Information to an Unauthorized Actor.
Which @angular/common versions are affected?
Affected versions include releases prior to 21.0.1, 20.3.14, 19.2.16 across affected packages: @angular/common.
What version fixes CVE-2025-66035?
Upgrading to 21.0.1, 20.3.14, 19.2.16 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @angular/common affected?
Yes, @angular/common is affected in releases prior to 21.0.1, 20.3.14, 19.2.16. Upgrade your dependency to 21.0.1, 20.3.14, 19.2.16 or later.
What CWE is associated with CVE-2025-66035?
CVE-2025-66035 is classified under CWE-359: Exposure of Private Personal Information to an Unauthorized Actor (The product does not properly prevent a person's private, personal information from being accessed by actors who either (1) are not explicitly authorized to access the information or (2) do not have the implicit consent of the person about whom the information is collected.).
How can I check npm dependencies for CVE-2025-66035?
Run the dependency tree command: 'npm ls @angular/common'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-58c5-g7wp-6w37",
  "modified" : "2026-06-09T10:55:35Z",
  "published" : "2025-11-26T23:18:50Z",
  "aliases" : [ "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.\n\nAngular'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.\n\n### Impact\nThe 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.\n\n### Attack Preconditions\n1. The victim's Angular application must have **XSRF protection enabled**.  \n2. 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.\n\n### Patches\n- 19.2.16\n- 20.3.14\n- 21.0.1\n\n### Workarounds\nDevelopers 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" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/common"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "21.0.0-next.0"
      }, {
        "fixed" : "21.0.1"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/common"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "20.0.0-next.0"
      }, {
        "fixed" : "20.3.14"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/common"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "19.2.16"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular/security/advisories/GHSA-58c5-g7wp-6w37"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-66035"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular/commit/0276479e7d0e280e0f8d26fa567d3b7aa97a516f"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular/commit/05fe6686a97fa0bcd3cf157805b3612033f975bc"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular/commit/3240d856d942727372a705252f7c8c115394a41e"
  }, {
    "type" : "WEB",
    "url" : "https://cert-portal.siemens.com/productcert/html/ssa-253495.html"
  }, {
    "type" : "WEB",
    "url" : "https://cert-portal.siemens.com/productcert/html/ssa-485750.html"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/angular/angular"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular/releases/tag/19.2.16"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular/releases/tag/20.3.14"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular/releases/tag/21.0.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-201", "CWE-359" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-11-26T23:18:50Z",
    "nvd_published_at" : "2025-11-26T23:15:49Z"
  }
}