PT-2026-104422

CVE-2026-104871

·

Published

2026-10-02

·

Updated

2026-10-06

Description by

CVSS 4.0
6.3
Medium
MetricsAV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Name of the Vulnerable Software and Affected Versions Angular SSR versions 17 through 18 Angular SSR versions prior to 20.3.36 Angular SSR versions prior to 21.2.23 Angular SSR versions prior to 22.1.7
Description An issue exists in the retrieveSSGPage logic within @angular/ssr/node and @angular/ssr on Windows deployments. The system accepts relative request URLs containing backslash parent-traversal segments. Because the resolve:// URL base preserves the backslash and path.join interprets it as a Windows separator, the pagePath.startsWith(normalize(publicPath)) check can be bypassed. This allows an unauthenticated requester to retrieve a sibling prerendered HTML page if that page contains the Angular SSG marker and the sibling output directory shares the configured public-directory prefix. This flaw is limited to instances where relative request URLs are passed to CommonEngine.render and does not allow arbitrary file read.
Recommendations Update to version 20.3.36 Update to version 21.2.23 Update to version 22.1.7 Avoid passing relative request URLs to CommonEngine.render as a temporary mitigation measure.
Exploitability
Exploit
Fix
Impacts
Researchers
Vendors
Affected products
Related identifiers
GHSA-7G7C-H8RR-7P6Q
Found an issue in the description? Have something to add? Feel free to write us 👾