{"id":"CVE-2025-66035","revision":"b93e74b0e2da4ac1b3252f0ce73d4d98","records":[{"revision":"b93e74b0e2da4ac1b3252f0ce73d4d98","observedAt":"2026-10-23T15:48:27.903+00:00","statement":{"source":"cve-program","id":"CVE-2025-66035","aliases":[],"title":"Angular HTTP Client Has XSRF Token Leakage via Protocol-Relative URLs","description":"Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. 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. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding 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-26T22:18:35.692+00:00","modifiedAt":"2026-06-02T13:00:29.58+00:00","affected":[{"ecosystem":"Vendor product","name":"angular","ranges":[],"versions":[],"rawVersionEvidence":"{\n                    \"vendor\": \"angular\",\n                    \"product\": \"angular\",\n                    \"versions\": [\n                        {\n                            \"version\": \">= 21.0.0-next.0, < 21.0.1\",\n                            \"status\": \"affected\"\n                        },\n                        {\n                            \"version\": \">= 20.0.0-next.0, < 20.3.14\",\n                            \"status\": \"affected\"\n                        },\n                        {\n                            \"version\": \"< 19.2.16\",\n                            \"status\": \"affected\"\n                        }\n                    ]\n                }"}],"metrics":[{"system":"CVSS 4.0","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":7.7,"severity":"HIGH"}],"references":["https://github.com/angular/angular/security/advisories/GHSA-58c5-g7wp-6w37","https://github.com/angular/angular/commit/0276479e7d0e280e0f8d26fa567d3b7aa97a516f","https://github.com/angular/angular/commit/05fe6686a97fa0bcd3cf157805b3612033f975bc","https://github.com/angular/angular/commit/3240d856d942727372a705252f7c8c115394a41e","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://www.cve.org/CVERecord?id=CVE-2025-66035","license":"CVE Program Terms of Use","key":"cve-program:CVE-2025-66035","identifiers":["CVE-2025-66035"]},"retained":false,"historicalAffected":[]}],"coverage":[]}