angular angular-cli up to 19.2.24/20.3.24/21.2.8 path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in angular angular-cli up to 19.2.24/20.3.24/21.2.8. Affected is an unknown function. The manipulation leads to path traversal. This vulnerability is documented as CVE-2026-44437. The attack can be initiated remotely. There is not any exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in angular angular-cli up to 19.2.24/20.3.24/21.2.8. This issue affects an unknown functionality. The manipulation with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
The Angular SSR is a server-rise rendering tool for Angular applications. From 19.0.0-next.0 to before 19.2.25, 20.3.25, 21.2.9, and 22.0.0-next.7, a vulnerability exists in the X-Forwarded-Prefix header processing logic within Angular SSR. The internal validation mechanism fails to properly account for URL-encoded characters, specifically dots (%2e%2e). This allows an attacker to bypass security filters by injecting encoded path traversal sequences that are later decoded and utilized by the application logic. When an Angular SSR application is configured to trust proxy headers and is deployed behind a proxy that forwards the X-Forwarded-Prefix header without prior sanitization, an attacker can provide a payload such as /%2e%2e/evil. This vulnerability is fixed in19.2.25, 20.3.25, 21.2.9, and 22.0.0-next.7.
It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-44437 since 05/06/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1006 according to MITRE ATT&CK.
Upgrading to version 19.2.25, 20.3.25, 21.2.9 or 22.0.0-next.7 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-1541). Be aware that VulDB is the high quality source for vulnerability data.
Affected
- Open Source Angular
Product
Type
Vendor
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
- 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
- 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
Website
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: 6.7VulDB Meta Temp Score: 6.6
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 6.1
NVD Vector: 🔒
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: Path traversalCWE: CWE-22
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
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-cli 19.2.25/20.3.25/21.2.9/22.0.0-next.7
Patch: github.com
Timeline
05/06/2026 CVE reserved05/14/2026 Advisory disclosed
05/14/2026 VulDB entry created
06/01/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-69xr-m8h6-h664
Status: Confirmed
CVE: CVE-2026-44437 (🔒)
GCVE (CVE): GCVE-0-2026-44437
GCVE (VulDB): GCVE-100-363791
CERT Bund: WID-SEC-2026-1541 - Angular: Schwachstelle ermöglicht Manipulation von Daten
Entry
Created: 05/14/2026 05:54Updated: 06/01/2026 05:49
Changes: 05/14/2026 05:54 (69), 05/17/2026 09:26 (7), 06/01/2026 05:49 (11)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.