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.