CVE-2026-111754

MEDIUMPre-NVD 5.15.1
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.0% (62nd 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

Also known asEUVD-2026-116377 (ENISA EUVD) · GHSA-w739-gvwx-grc3 (GitHub Security Advisories)Source: ENISA EUVD

5.1EG
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: 1.0%CVSS: 5.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.33, 21.2.25, and 22.2.1, ServerPlatformLocation in Angular server-side rendering checks for protocol-relative URLs before WHATWG URL normalization. A request path containing a popping dot segment followed by multiple slashes can bypass the raw resolveUrl check and normalize to a pathname beginning with two slashes. When Angular SSR detects a mismatch with the router's final location, it can place that pathname in an HTTP Location header, causing a browser to navigate to an attacker-controlled origin. Affected applications use @angular/platform-server and @angular/ssr and either expose compatible parameter or child route shapes or pass user-controlled navigation targets through infrastructure that preserves the relevant dot segments or semicolons. Pure client-side SPAs are not affected. This issue is fixed in versions 20.3.33, 21.2.25, and 22.2.1.

CVSS
5.1
EG Score
5.1MEDIUMmedium confidence
EG Risk
23
EG Risk 23/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)
Severity51% × 45%
Impact severity (EG Severity): CVSS 5.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.0% × 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
1.0%
EPSS %ILE
62nd
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 (5.1): severity, escalated by confirmed exploitation. This CVE's 5.1 is its impact severity (EG Severity), not escalated.

EG Severity
5.1 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
1.0% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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 20, 2026

Last Modified

November 12, 2026

References (11)

Vendor Advisories for CVE-2026-111754(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/platform-server @ 22.2.1 (fixes >= 22.0.0, < 22.2.1)—ghsa
npm@angular/platform-server @ 21.2.25 (fixes >= 21.0.0, < 21.2.25)—ghsa
npm@angular/platform-server @ 20.3.33 (fixes >= 20.0.0, < 20.3.33)—ghsa
npm@angular/platform-server—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/platform-server—
  • 22.0.0 up to 22.2.1: fixed in 22.2.1
  • 21.0.0 up to 21.2.25: fixed in 21.2.25
  • 20.0.0 up to 20.3.33: fixed in 20.3.33
  • every version through 19.2.25: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 18× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  2. 2026-11-12 20:08 UTCEchelonGraph re-scored
  3. 2026-11-12 20:08 UTCGHSA enrichmentGHSA-w739-gvwx-grc3 · GitHub severity MODERATE
  4. 2026-11-12 16:33 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  5. 2026-11-11 16:38 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  6. 2026-11-11 06:40 UTCEchelonGraph re-scored
  7. 2026-11-11 06:40 UTCGHSA enrichmentGHSA-w739-gvwx-grc3 · GitHub severity MODERATE
  8. 2026-11-10 16:42 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  9. 2026-11-09 16:34 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  10. 2026-11-08 16:38 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  11. 2026-11-07 16:38 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  12. 2026-11-06 16:36 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  13. 2026-11-05 16:36 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  14. 2026-11-04 16:34 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  15. 2026-11-03 22:32 UTCEchelonGraph re-scored
  16. 2026-11-03 22:32 UTCGHSA enrichmentGHSA-w739-gvwx-grc3 · GitHub severity MODERATE
  17. 2026-11-03 22:12 UTCENISA EUVD ID recordedEUVD-2026-116377 · Source: ENISA EUVD
  18. 2026-11-03 21:30 UTCEchelonGraph re-scored
  19. 2026-11-03 21:30 UTCGHSA enrichmentGHSA-w739-gvwx-grc3 · GitHub severity MODERATE
  20. 2026-11-03 21:01 UTCEchelonGraph re-scoredFirst assessed: 5.1 MEDIUM
  21. 2026-11-03 21:01 UTCGHSA enrichmentGHSA-w739-gvwx-grc3 · GitHub severity MODERATE
  22. 2026-11-03 21:01 UTCMITRE cvelistV5CVSS → 5.1 · CVSS v4 → 5.1
  23. 2026-11-01 07:59 UTCGHSA enrichmentGHSA-w739-gvwx-grc3 · GitHub severity MODERATE
  24. 2026-10-25 14:52 UTCEchelonGraph re-scored
  25. 2026-10-20 15:20 UTCEchelonGraph re-scored

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-111754?
CVE-2026-111754 is a medium-severity vulnerability; its CVE record was published on October 20, 2026. Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.33, 21.2.25, and 22.2.1, ServerPlatformLocation in Angular server-side rendering checks for protocol-relative URLs before WHATWG URL normalization. A…
When was the CVE record for CVE-2026-111754 published?
The CVE record for CVE-2026-111754 was published on October 20, 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 November 12, 2026; the record at its source may have been updated since.
Is CVE-2026-111754 actively exploited?
CVE-2026-111754 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (62nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-111754?
CVE-2026-111754 has a CVSS base score of 5.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-111754?
A fix for CVE-2026-111754 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-111754 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-111754

Explore →

Is Your Infrastructure Affected by CVE-2026-111754?

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

Book a Demo →Browse All CVEs