Skip to content
Connect AISign inSign up free
CVE-2026-1048716.3MediumCWE-22

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

angular · angular-cli

Affected: angular-cli · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.4%probability of exploitation in the next 30 days
37th percentile
050100

Higher than 37% of scored CVEs

6.3MediumCVSS 4.0
LowMedium

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • angular · angular-cli< 20.3.36; >= 21.0.0, < 21.2.23; >= 22.0.0, < 22.1.7

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Vendor
angular
Published
October 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-104871 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References