{"id":"GHSA-58c5-g7wp-6w37","revision":"6f145e27e2a1455cb38b312faabaf8ba","records":[{"revision":"6f145e27e2a1455cb38b312faabaf8ba","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"GHSA-58c5-g7wp-6w37","aliases":["CVE-2025-66035"],"title":"Angular is Vulnerable to XSRF Token Leakage via Protocol-Relative URLs in Angular HTTP Client","description":"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.","state":0,"publishedAt":"2025-11-26T23:18:50+00:00","modifiedAt":"2026-09-10T03:50:30.5638804+00:00","affected":[{"ecosystem":"npm","name":"@angular/common","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"21.0.0-next.0"},{"kind":"fixed","version":"21.0.1"}]}],"versions":[],"rawVersionEvidence":null},{"ecosystem":"npm","name":"@angular/common","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"20.0.0-next.0"},{"kind":"fixed","version":"20.3.14"}]}],"versions":[],"rawVersionEvidence":null},{"ecosystem":"npm","name":"@angular/common","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"fixed","version":"19.2.16"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V4","vector":"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","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"HIGH"}],"references":["https://github.com/angular/angular/security/advisories/GHSA-58c5-g7wp-6w37","https://nvd.nist.gov/vuln/detail/CVE-2025-66035","https://github.com/angular/angular/commit/0276479e7d0e280e0f8d26fa567d3b7aa97a516f","https://github.com/angular/angular/commit/05fe6686a97fa0bcd3cf157805b3612033f975bc","https://github.com/angular/angular/commit/3240d856d942727372a705252f7c8c115394a41e","https://cert-portal.siemens.com/productcert/html/ssa-253495.html","https://cert-portal.siemens.com/productcert/html/ssa-485750.html","https://github.com/angular/angular","https://github.com/angular/angular/releases/tag/19.2.16","https://github.com/angular/angular/releases/tag/20.3.14","https://github.com/angular/angular/releases/tag/21.0.1"],"sourceUrl":"https://github.com/advisories/GHSA-58c5-g7wp-6w37","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-58c5-g7wp-6w37","identifiers":["GHSA-58c5-g7wp-6w37","CVE-2025-66035"]},"retained":false,"historicalAffected":[]}],"coverage":[]}