CVE-2026-126954

MEDIUMPre-NVD 4.74.7
EchelonGraph scoreHIGH confidence

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

Score 4.7 from GitHub Security Advisory (severity: LOW) published 2026-11-13. A secondary CVSS source baseline 4.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-125111 (ENISA EUVD) · GHSA-c2c3-mpf8-3933 (GitHub Security Advisories)Source: ENISA EUVD

4.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 4.7Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Glance from 0.7.9 before 0.8.8 contains a stored cross-site scripting vulnerability that allows malicious extension endpoints to inject javascript: URLs via the Widget-Title-URL response header. Attackers controlling an extension endpoint can execute script when users click the widget title, reading dashboard pages through same-origin requests and exfiltrating content.

CVSS v3
4.7
EG Score
4.7MEDIUMhigh confidence
EG Risk
37
EG Risk 37/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)
Severity47% × 45%
Impact severity (EG Severity): CVSS 4.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (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.3%
EPSS %ILE
27th
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 (4.7): severity, escalated by confirmed exploitation. This CVE's 4.7 is its impact severity (EG Severity), not escalated.

EG Severity
4.7 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS. 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 low or medium mission impact; Track* at high (mission-essential systems).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 low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation public PoC (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

November 13, 2026

Last Modified

November 17, 2026

Advisory Details (7)

Auto-updated Nov 13, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
Web page

Glance 0.7.9 before 0.8.8 Stored XSS via Widget-Title-URL Header | Advisories | VulnCheck

https://www.vulncheck.com/advisories/glance-0.7.9-before-0.8.8-stored-xss-via-widget-title-url-header
GitHub advisoryMentions a patch (unverified)

Stored XSS via extension widget Widget-Title-URL header (safeURL scheme-filter bypass) · Advisory · glanceapp/glance · GitHub

https://github.com/glanceapp/glance/security/advisories/GHSA-f2c4-p935-ffpj
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

An attacker-controlled extension endpoint can store a `javascript:` URL in the Glance dashboard by returning it in the `Widget-Title-URL` response header. Glance renders that value into the widget's title-link `href` through `safeURL`, which disables Go's URL sanitizer, so the scheme survives into the DOM. When any authenticated user clicks the widget title, attacker JavaScript runs in the Glance origin and can read and exfiltrate every page the victim is allowed to see — including the `Secret...

An attacker-controlled extension endpoint can store a `javascript:` URL in the Glance dashboard by returning it in the `Widget-Title-URL` response header. Glance renders that value into the widget's title-link `href` through `safeURL`, which disables Go's URL sanitizer, so the scheme survives into the DOM. When any authenticated user clicks the widget title, attacker JavaScript runs in the Glance origin and can read and exfiltrate every page the victim is allowed to see — including the `Secret Page` — by issuing authenticated same-origin requests. The `allow-potentially-dangerous-html` switch that users rely on to make extensions safe does **not** cover this sink. · Advisory · glanceapp/glance · GitHub

https://github.com/glanceapp/glance/security/advisories/GHSA-96x7-3hwp-rcfc
GitHub release Patch Available

v0.8.8

Patch available: glanceapp/glance v0.8.8

https://github.com/glanceapp/glance/releases/tag/v0.8.8
GitHub commit

commit e19081cfa029 (glanceapp/glance)

Fix landed in glanceapp/glance commit e19081cfa029 — awaiting tagged release

https://github.com/glanceapp/glance/commit/e19081cfa029edbe16b1354ffe03076a8cdf0244
Web page

glance/internal/glance/widget-extension.go at v0.8.7 · glanceapp/glance · GitHub

https://github.com/glanceapp/glance/blob/v0.8.7/internal/glance/widget-extension.go#L151-L152
Web page

glance/internal/glance/templates/widget-base.html at v0.8.7 · glanceapp/glance · GitHub

https://github.com/glanceapp/glance/blob/v0.8.7/internal/glance/templates/widget-base.html#L5

Vendor Advisories for CVE-2026-126954(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 17× 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 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). "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-21 16:38 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  3. 2026-11-20 05:39 UTCEchelonGraph re-scored
  4. 2026-11-20 05:39 UTCGHSA enrichmentGHSA-c2c3-mpf8-3933 · GitHub severity LOW · GitHub CVSS 4.7
  5. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  6. 2026-11-18 16:34 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  7. 2026-11-17 19:42 UTCEchelonGraph re-scored
  8. 2026-11-17 19:42 UTCGHSA enrichmentGHSA-c2c3-mpf8-3933 · GitHub severity LOW · GitHub CVSS 4.7
  9. 2026-11-17 19:28 UTCEchelonGraph re-scored
  10. 2026-11-17 19:28 UTCGHSA enrichmentGHSA-c2c3-mpf8-3933 · GitHub severity LOW · GitHub CVSS 4.7
  11. 2026-11-17 18:58 UTCEchelonGraph re-scored
  12. 2026-11-17 18:58 UTCGHSA enrichmentGHSA-c2c3-mpf8-3933 · GitHub severity LOW · GitHub CVSS 4.7
  13. 2026-11-17 16:34 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  14. 2026-11-16 16:49 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  15. 2026-11-15 16:57 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  16. 2026-11-14 16:39 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  17. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  18. 2026-11-13 16:14 UTCGHSA enrichmentGHSA-c2c3-mpf8-3933 · GitHub severity LOW · GitHub CVSS 4.7
  19. 2026-11-13 12:55 UTCEchelonGraph re-scored
  20. 2026-11-13 12:55 UTCGHSA enrichmentGHSA-c2c3-mpf8-3933 · GitHub severity LOW · GitHub CVSS 4.7
  21. 2026-11-13 10:33 UTCEchelonGraph re-scored
  22. 2026-11-13 10:01 UTCENISA EUVD ID recordedEUVD-2026-125111 · Source: ENISA EUVD
  23. 2026-11-13 09:38 UTCEchelonGraph re-scoredFirst assessed: 4.7 MEDIUM
  24. 2026-11-13 09:36 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-126954?
CVE-2026-126954 is a medium-severity vulnerability; its CVE record was published on November 13, 2026. Glance from 0.7.9 before 0.8.8 contains a stored cross-site scripting vulnerability that allows malicious extension endpoints to inject javascript: URLs via the Widget-Title-URL response header. Attackers controlling an extension endpoint can execute script when users click the widget title,…
When was CVE-2026-126954 made public?
CVE-2026-126954 was made public on November 7, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on November 13, 2026. EchelonGraph's copy of the record carries a last-modified date of November 17, 2026; the record at its source may have been updated since.
Is CVE-2026-126954 actively exploited?
CVE-2026-126954 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-126954?
CVE-2026-126954 has a CVSS base score of 4.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-126954?
A fix for CVE-2026-126954 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-126954 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-126954?

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