Angular: XSRF Token Leakage via URL Parsing Discrepancy in Angular HTTP Client (Incomplete fix for CVE-2025-66035)
- Exploited
- No known exploitation
- Fix
- Fixed in 20.3.34, 21.0.3
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 20.3.34, 21.0.3.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 13/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Angular's HttpClient (the @angular/common library used in web apps) can leak the XSRF token that protects a user's session when XSRF protection is enabled. A remote attacker can trigger this without logging in, but the victim must take some action, such as visiting an attacker-controlled page, for the token to be exposed.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.34 and 21.0.3, the @angular/common HttpClient function xsrfInterceptorFn uses a regular expression that does not normalize request URLs in the same way as the browser's WHATWG URL parser. With XSRF protection enabled, a mutating HTTP request to an attacker-controlled URL containing backslashes, stripped control characters or spaces, or removable ASCII whitespace can be misclassified as relative and same-origin, causing the interceptor to attach the X-XSRF-TOKEN header before the browser dispatches the request to a cross-origin host. With permissive CORS handling for the custom header, the attacker can obtain the victim's XSRF token and use it to perform cross-site request forgery against the victim session. This issue is fixed in versions 20.3.34 and 21.0.3.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.9/10CVSS 5.9
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 20.3.34, 21.0.3.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- angular angular
through 19.2.25; From 20.0.0 · fixed in 20.3.34; From 21.0.0 · fixed in 21.0.3
Evidence 8
- Advisory
- Repository
- Repository
- Repository
- Repository
Show all 8 sourcesShow fewer sources
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-111753
Is CVE-2026-111753 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-111753?
angular: through 19.2.25; from 20.0.0 before 20.3.34; from 21.0.0 before 21.0.3.Source: cve.now feed data
How do I fix CVE-2026-111753?
Upgrade to a fixed version: 20.3.34, 21.0.3.Source: cve.now feed data