CVE-2026-104871

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (34th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
33
EG Risk 33/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity63% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 2, 2026

Last Modified

October 2, 2026

Advisory Details (8)

Auto-updated Oct 2, 2026
Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

22.1.7

Patch available: angular/angular-cli v22.1.7

https://github.com/angular/angular-cli/releases/tag/v22.1.7
github_release Patch Available

21.2.23

Patch available: angular/angular-cli v21.2.23

https://github.com/angular/angular-cli/releases/tag/v21.2.23
github_release Patch Available

20.3.36

Patch available: angular/angular-cli v20.3.36

https://github.com/angular/angular-cli/releases/tag/v20.3.36
github_commit Patch Available

commit c3e5982e4970 (angular/angular-cli)

Patch available: angular/angular-cli v20.3.36 (contains commit c3e5982e4970)

https://github.com/angular/angular-cli/commit/c3e5982e49705f0f6a913cb94622b4c555d2d914
github_commit Patch Available

commit bb72145f9ab4 (angular/angular-cli)

Patch available: angular/angular-cli v22.2.0-next.6 (contains commit bb72145f9ab4)

https://github.com/angular/angular-cli/commit/bb72145f9ab45aee29f523236b3a25cd0813a841
github_commit Patch Available

commit 70748ca8e76f (angular/angular-cli)

Patch available: angular/angular-cli v22.1.7 (contains commit 70748ca8e76f)

https://github.com/angular/angular-cli/commit/70748ca8e76fe4b42798719410336119d943e755
github_commit Patch Available

commit 645e41a47d21 (angular/angular-cli)

Patch available: angular/angular-cli v21.2.23 (contains commit 645e41a47d21)

https://github.com/angular/angular-cli/commit/645e41a47d21b7651837a4250de99af0509626e2
github Patch Available

Path Traversal to Sibling Directories in `CommonEngine` on Windows · Advisory · angular/angular-cli · GitHub

https://github.com/angular/angular-cli/security/advisories/GHSA-7g7c-h8rr-7p6q

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 5× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-03 21:51 UTCEG score recompute
  2. 2026-10-03 14:25 UTCEPSS rescore
  3. 2026-10-02 20:20 UTCEG score recompute
  4. 2026-10-02 19:46 UTCEG score recompute
  5. 2026-10-02 19:45 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-104871?
CVE-2026-104871 is a medium vulnerability published on October 2, 2026. 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…
When was CVE-2026-104871 disclosed?
CVE-2026-104871 was first published on October 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-104871 actively exploited?
CVE-2026-104871 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-104871?
CVE-2026-104871 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-104871?
A fix for CVE-2026-104871 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-104871

Explore →

Is Your Infrastructure Affected by CVE-2026-104871?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs