Answer in brief
CVE-2026-111753 records a Medium severity (CVSS 5.9) vulnerability in Angular: XSRF Token Leakage via URL Parsing Discrepancy in Angular HTTP Client (Incomplete fix for CVE-2025-66035). The current sources do not mark it as known exploited. The current feed maps angular/angular (generic), @angular/common (npm), @angular/common (npm), @angular/common (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps angular/angular (generic), @angular/common (npm), @angular/common (npm), @angular/common (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| angular/angulargeneric | <=19.2.25 || >=20.0.0 <20.3.34 || >=21.0.0 <21.0.3 | = 19.2.25, 20.3.34, 21.0.3 |
| @angular/commonnpm | >=20.0.0,<20.3.34 | 20.3.34 |
| @angular/commonnpm | <=19.2.25 | Not reported |
| @angular/commonnpm | >=21.0.0,<21.0.3 | 21.0.3 |
| @angular/commonnpm | >=21.0.0 <21.0.3 | 21.0.3 |
| @angular/commonnpm | >=20.0.0 <20.3.34 | 20.3.34 |
| @angular/commonnpm | >=0 | Not reported |
Published upstream
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 20, 2026
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.
Quoted source text, attributed separately from HOL analysis.