CVE-2026-111753: angular · Insertion of Sensitive Information Into Sent Data
Affects angularSource CVE Database V5
Not known to be exploited · CVSS 5.9 Medium : upgrade to 21.0.3 or 20.3.34 when convenient.
Data as of 5 Nov 2026, 20:33 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 5.9 |
|---|
- Patch
- Available – fixed in 21.0.3, 20.3.34
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 5 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade angular to 21.0.3 or 20.3.34.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| angularangular | Affected
| Fixed in
|
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.
References
- github.com/angular/angular/security/advisories/GHSA-jfgx-762w-99vr (opens in a new tab)
- github.com/angular/angular/issues/71294 (opens in a new tab)
- github.com/angular/angular/pull/65683 (opens in a new tab)
- github.com/angular/angular/pull/71295 (opens in a new tab)
- github.com/angular/angular/commit/20474d3f0fd7c64071add6e84acf720627e5c19b (opens in a new tab)
- github.com/angular/angular/commit/933ce817d53e25926844fa56af8230816763d08e (opens in a new tab)
- github.com/angular/angular/releases/tag/21.0.3 (opens in a new tab)
- github.com/angular/angular/releases/tag/v20.3.34 (opens in a new tab)