CVE-2026-104871

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (36th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-91778 (ENISA EUVD) · GHSA-7g7c-h8rr-7p6q (GitHub Security Advisories)Source: ENISA EUVD

6.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • 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
29
EG Risk 29/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity63% × 45%
Impact severity (EG Severity): CVSS 6.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
36th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.3): severity, escalated by confirmed exploitation. This CVE's 6.3 is its impact severity (EG Severity), not escalated.

EG Severity
6.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 2, 2026

Last Modified

October 6, 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 advisoryMentions a patch (unverified)

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

Vendor Advisories for CVE-2026-104871(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npm@angular/ssr @ 22.1.7 (fixes >= 22.0.0, < 22.1.7)—ghsa
npm@angular/ssr @ 21.2.23 (fixes >= 21.0.0, < 21.2.23)—ghsa
npm@angular/ssr @ 20.3.36 (fixes >= 20.0.0, < 20.3.36)—ghsa
npm@angular/ssr—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@angular/ssr—
  • 22.0.0 up to 22.1.7: fixed in 22.1.7
  • 21.0.0 up to 21.2.23: fixed in 21.2.23
  • 20.0.0 up to 20.3.36: fixed in 20.3.36
  • every version through 19.2.27: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 45× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  2. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-7g7c-h8rr-7p6q · GitHub severity MODERATE
  3. 2026-11-01 08:00 UTCEG score recompute
  4. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  5. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  6. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  7. 2026-10-29 14:52 UTCEG score recompute
  8. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  10. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  11. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  12. 2026-10-25 14:55 UTCEG score recompute
  13. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  14. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  15. 2026-10-23 09:16 UTCEG score recompute
  16. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  17. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  18. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  20. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  21. 2026-10-18 05:09 UTCEG score recompute
  22. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  23. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  24. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  25. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
Show 23 more
  1. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  2. 2026-10-12 16:40 UTCEG score recompute
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  4. 2026-10-11 20:15 UTCEG score recompute
  5. 2026-10-11 18:27 UTCEG score recompute
  6. 2026-10-11 15:01 UTCEG score recompute
  7. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  8. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  9. 2026-10-10 18:21 UTCEG score recompute
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  11. 2026-10-08 17:32 UTCEG score recompute
  12. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  13. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  14. 2026-10-06 16:21 UTCEG score recompute
  15. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  16. 2026-10-05 22:43 UTCEG score recompute
  17. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  18. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  19. 2026-10-03 21:51 UTCEG score recompute
  20. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  21. 2026-10-02 20:20 UTCEG score recompute
  22. 2026-10-02 19:46 UTCEG score recomputeFirst assessed: 6.3 MEDIUM
  23. 2026-10-02 19:45 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-104871?
CVE-2026-104871 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-104871 published?
The CVE record for CVE-2026-104871 was published on October 2, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 6, 2026; the record at its source may have been updated since.
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 (36th 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. The vendor advisories EchelonGraph has for CVE-2026-104871 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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