Angular: SSRF and Cross-Origin Credential Disclosure via URL Resolution Discrepancy in SSR
angular
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @angular/platform-server npm |
|
|
Original description
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.30, 21.2.22, and 22.1.4, Angular Server-Side Rendering in @angular/platform-server processes user-controlled resource or request URLs through HttpClient after application code validates them with WHATWG URL parsing. The resolveUrl and parseUrl utilities called String.prototype.trim(), which removed leading Unicode whitespace such as U+00A0 or U+FEFF after the input passed a same-origin check, converting a relative path into a protocol-relative attacker-controlled URL. In affected applications that attach sensitive server-side credentials such as Authorization headers to approved requests, relativeUrlsTransformerInterceptorFn then dispatched the request to the attacker-controlled origin, causing SSRF and credential disclosure. This issue is fixed in versions 20.3.30, 21.2.22, and 22.1.4.
From the CVE record · GitHub_M
References
- github.com/angular/angular/security/advisories/GHSA-f6mr-pjwc-34m4Vendor advisory
- github.com/angular/angular/commit/3e924cc8dbbb57f23b262cb8f0d7e2bd0673034cPatch
- github.com/angular/angular/commit/5aa6d97deb9ef1de14e23748b7fa74f97d183132Patch
- github.com/angular/angular/commit/71e52d1396b9cef98652929b73e08c4cde645970Patch
- github.com/angular/angular/releases/tag/v20.3.30Release notes
- github.com/angular/angular/releases/tag/v21.2.22Release notes
- github.com/angular/angular/releases/tag/v22.1.4Release notes
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/88xxx/CVE-2026-88056.json
- nvd.nist.gov/vuln/detail/CVE-2026-88056
- github.com/angular/angular/commit/9339a7a2de437ed93f9cc3da7f32d0100412d599
- github.com/angular/angular