{"id":"CVE-2026-104871","revision":"532d06a2eb794211a3d2d13b07e6dfaa","records":[{"revision":"532d06a2eb794211a3d2d13b07e6dfaa","observedAt":"2026-10-23T15:48:27.903+00:00","statement":{"source":"cve-program","id":"CVE-2026-104871","aliases":[],"title":"Angular SSR: Path Traversal to Sibling Directories in CommonEngine on Windows","description":"The Angular SSR is a server-rise rendering tool for Angular applications. Prior to versions 20.3.36, 21.2.23, and 22.1.7, the CommonEngine retrieveSSGPage prerendered-page retrieval logic in @angular/ssr/node, and in @angular/ssr for versions 17 through 18, accepts a relative request URL containing a backslash parent-traversal segment on Windows. The non-special resolve:// URL base preserves the backslash, path.join interprets it as a Windows separator, and the pagePath.startsWith(normalize(publicPath)) check incorrectly accepts a sibling output directory whose name shares the configured public-directory prefix. An unauthenticated requester can therefore retrieve a sibling prerendered HTML page when that page contains the Angular SSG marker. The issue is limited to Windows deployments that pass relative request URLs to CommonEngine.render, have a prefix-sharing sibling output directory, and contain qualifying prerendered Angular HTML; it does not provide arbitrary file read. This issue is fixed in versions 20.3.36, 21.2.23, and 22.1.7.","state":0,"publishedAt":"2026-10-02T19:43:50.475+00:00","modifiedAt":"2026-10-02T20:12:49.364+00:00","affected":[{"ecosystem":"Vendor product","name":"angular-cli","ranges":[],"versions":[],"rawVersionEvidence":"{\n                    \"vendor\": \"angular\",\n                    \"product\": \"angular-cli\",\n                    \"versions\": [\n                        {\n                            \"version\": \"< 20.3.36\",\n                            \"status\": \"affected\"\n                        },\n                        {\n                            \"version\": \">= 21.0.0, < 21.2.23\",\n                            \"status\": \"affected\"\n                        },\n                        {\n                            \"version\": \">= 22.0.0, < 22.1.7\",\n                            \"status\": \"affected\"\n                        }\n                    ]\n                }"}],"metrics":[{"system":"CVSS 4.0","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","score":6.3,"severity":"MEDIUM"}],"references":["https://github.com/angular/angular-cli/security/advisories/GHSA-7g7c-h8rr-7p6q","https://github.com/angular/angular-cli/commit/645e41a47d21b7651837a4250de99af0509626e2","https://github.com/angular/angular-cli/commit/70748ca8e76fe4b42798719410336119d943e755","https://github.com/angular/angular-cli/commit/bb72145f9ab45aee29f523236b3a25cd0813a841","https://github.com/angular/angular-cli/commit/c3e5982e49705f0f6a913cb94622b4c555d2d914","https://github.com/angular/angular-cli/releases/tag/v20.3.36","https://github.com/angular/angular-cli/releases/tag/v21.2.23","https://github.com/angular/angular-cli/releases/tag/v22.1.7"],"sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-104871","license":"CVE Program Terms of Use","key":"cve-program:CVE-2026-104871","identifiers":["CVE-2026-104871"]},"retained":false,"historicalAffected":[]}],"coverage":[]}