Shellfeed logo Shellfeed

CVE-2026-111753 · MEDIUM

Summary: Angular: XSRF Token Leakage via URL Parsing Discrepancy in Angular HTTP Client (Incomplete fix for CVE-2025-66035)

EPSS: 0.5% probability of exploitation in the next 30 days (percentile 45.8).

Details

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.

Severity

MEDIUM — vector CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Affected packages

  • npm @angular/common [21.0.0 – 21.0.3]
  • npm @angular/common [20.0.0 – 20.3.34]
  • npm @angular/common [0 – 19.2.25]
  • GIT github.com/angular/angular [0 – 6d1753b46b7389c10aa17da2327043fbf5296035] [40e2b5b4d13792ed7c46a1d22afcf6c12ac9c679 – 329172858b99ab3910b15c1e79bd49b0d5094b30] [00dcbf2eeb3fd18ed39148e4bc9e49a5b35cae0c – c355ffd99e691fffe5a53e5069d8fc4291676869]

References

Posts about CVE-2026-111753