Angular up to 19.2.25/20.3.29/21.2.21/22.1.3 Server-Side Rendering String.prototype.trim server-side request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 1.47+ |
Summary
A vulnerability was found in Angular up to 19.2.25/20.3.29/21.2.21/22.1.3. It has been classified as problematic. This issue affects the function String.prototype.trim of the component Server-Side Rendering. The manipulation leads to server-side request forgery.
This vulnerability is uniquely identified as CVE-2026-88056. The attack is possible to be carried out remotely. No exploit exists.
Upgrading the affected component is recommended.
Details
A vulnerability was found in Angular up to 19.2.25/20.3.29/21.2.21/22.1.3 and classified as problematic. This issue affects the function String.prototype.trim of the component Server-Side Rendering. The manipulation with an unknown input leads to a server-side request forgery vulnerability. Using CWE to declare the problem leads to CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. Impacted is confidentiality. The summary by CVE is:
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.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-88056 since 09/09/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.
Upgrading to version 20.3.30, 21.2.22 or 22.1.4 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
- 19.2.0
- 19.2.1
- 19.2.2
- 19.2.3
- 19.2.4
- 19.2.5
- 19.2.6
- 19.2.7
- 19.2.8
- 19.2.9
- 19.2.10
- 19.2.11
- 19.2.12
- 19.2.13
- 19.2.14
- 19.2.15
- 19.2.16
- 19.2.17
- 19.2.18
- 19.2.19
- 19.2.20
- 19.2.21
- 19.2.22
- 19.2.23
- 19.2.24
- 19.2.25
- 20.3.0
- 20.3.1
- 20.3.2
- 20.3.3
- 20.3.4
- 20.3.5
- 20.3.6
- 20.3.7
- 20.3.8
- 20.3.9
- 20.3.10
- 20.3.11
- 20.3.12
- 20.3.13
- 20.3.14
- 20.3.15
- 20.3.16
- 20.3.17
- 20.3.18
- 20.3.19
- 20.3.20
- 20.3.21
- 20.3.22
- 20.3.23
- 20.3.24
- 20.3.25
- 20.3.26
- 20.3.27
- 20.3.28
- 20.3.29
- 21.2.0
- 21.2.1
- 21.2.2
- 21.2.3
- 21.2.4
- 21.2.5
- 21.2.6
- 21.2.7
- 21.2.8
- 21.2.9
- 21.2.10
- 21.2.11
- 21.2.12
- 21.2.13
- 21.2.14
- 21.2.15
- 21.2.16
- 21.2.17
- 21.2.18
- 21.2.19
- 21.2.20
- 21.2.21
- 22.1.0
- 22.1.1
- 22.1.2
- 22.1.3
Website
- Product: https://github.com/angular/angular/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Server-side request forgeryCWE: CWE-918
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Angular 20.3.30/21.2.22/22.1.4
Timeline
09/09/2026 CVE reserved09/10/2026 Advisory disclosed
09/10/2026 VulDB entry created
09/10/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-88056 (🔒)
GCVE (CVE): GCVE-0-2026-88056
GCVE (VulDB): GCVE-100-402197
Entry
Created: 09/10/2026 21:04Changes: 09/10/2026 21:04 (68)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.