EdgeEver 1.6.0 through 1.112.0 contains a stored cross-site scripting vulnerability in TemplatesPane.tsx that renders template contentMarkdown with raw HTML via dangerouslySetInnerHTML without sanitization. Attackers can write templates containing HTML event handlers through an API or MCP token to run script on preview and access the privileged window.edgeeverDesktop bridge.
CVE-2026-109558
HIGHPre-NVD 8.78.7Trending — 4 sources updated this weekElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: CISA's SSVC exploitation value: public PoC.EchelonGraph confidence 38%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 8.7 from GitHub Security Advisory (severity: HIGH) published 2026-10-12. A secondary CVSS source baseline 8.7; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
8.7EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (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: 8.7Exploit: No code on recordExposed services: Not assessed
An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.
- CVSS v3
- 8.7
- EG Score
- 8.7HIGHhigh confidence
- EG Risk
- 55EG Risk 55/100
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 (value × EchelonGraph’s weight)Severity87% × 45%The EG Score, 8.7 of 10.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, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release. - EPSS PROB
- 0.3%
- EPSS %ILE
- 24th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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 12, 2026
Last Modified
October 13, 2026
Advisory Details (6)
Auto-updated Oct 12, 2026🔬 Proof of concept available. Upstream fix merged — awaiting tagged release. Sources: github_commit.
Web page
EdgeEver 1.6.0 through 1.112.0 Stored XSS via TemplatesPane Template Preview | Advisories | VulnCheck
https://www.vulncheck.com/advisories/edgeever-1.6.0-through-1.112.0-stored-xss-via-templatespane-template-previewWeb page
GitHub - tianma-if/edgeever: Open-source, AI-native knowledge base & Evernote alternative with native MCP. Zero-cost on Cloudflare or Docker. · GitHub
https://github.com/tianma-if/edgeeverWeb page
edgeever/apps/web/src/components/TemplatesPane.tsx at f6ade70423ba366077653dbb8ac43a677933c776 · tianma-if/edgeever · GitHub
https://github.com/tianma-if/edgeever/blob/f6ade70423ba366077653dbb8ac43a677933c776/apps/web/src/components/TemplatesPane.tsx#L150-L158GitHub commit
commit 6b5027e8b4be (tianma-if/edgeever)
Fix landed in tianma-if/edgeever commit 6b5027e8b4be — awaiting tagged release
https://github.com/tianma-if/edgeever/commit/6b5027e8b4becbee0c0de7cd1a3d04af78ca87caWeb page
桌面客户端安全加固与发布跟踪（#532–#543） · Issue #546 · tianma-if/edgeever · GitHub
https://github.com/tianma-if/edgeever/issues/546Web page🟡 PoC Available
[漏洞反馈][CRITICAL] vuln-0046 | 存储型XSS：模板预览未经净化（marked → dangerouslySetInnerHTML），直达特权桥 · Issue #533 · tianma-if/edgeever · GitHub
https://github.com/tianma-if/edgeever/issues/533Vendor Advisories for CVE-2026-109558(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 / 10× 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.
- 2026-10-13 18:28 UTCEG score recompute
- 2026-10-13 18:28 UTCGHSA enrichmentGHSA-f2xf-xr5r-qf3x · GitHub severity HIGH · GitHub CVSS 8.7
- 2026-10-13 18:26 UTCEG score recompute
- 2026-10-13 18:26 UTCGHSA enrichmentGHSA-f2xf-xr5r-qf3x · GitHub severity HIGH · GitHub CVSS 8.7
- 2026-10-13 17:52 UTCEG score recompute
- 2026-10-13 17:52 UTCGHSA enrichmentGHSA-f2xf-xr5r-qf3x · GitHub severity HIGH · GitHub CVSS 8.7
- 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-10-12 21:26 UTCEG score recompute
- 2026-10-12 21:02 UTCEG score recomputeFirst assessed: 8.7 HIGH
- 2026-10-12 20:59 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-109558?
CVE-2026-109558 is a high-severity vulnerability; its CVE record was published on October 12, 2026. EdgeEver 1.6.0 through 1.112.0 contains a stored cross-site scripting vulnerability in TemplatesPane.tsx that renders template contentMarkdown with raw HTML via dangerouslySetInnerHTML without sanitization. Attackers can write templates containing HTML event handlers through an API or MCP token to…
When was CVE-2026-109558 made public?
CVE-2026-109558 was made public on October 12, 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 October 12, 2026. EchelonGraph's copy of the record carries a last-modified date of October 13, 2026; the record at its source may have been updated since.
Is CVE-2026-109558 actively exploited?
CVE-2026-109558 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (24th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-109558?
CVE-2026-109558 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-109558?
An upstream fix for CVE-2026-109558 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-109558 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-109558
Is Your Infrastructure Affected by CVE-2026-109558?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.