CVE-2026-54067

CRITICALPre-NVD 9.99.9
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (31st 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
Elevated

Also known asEUVD-2026-39123 (ENISA EUVD) · GHSA-mvjr-vv3c-w4qv (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan a fixRemediate 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.4%CVSS: 9.9Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

SiYuan is an open-source personal knowledge management system. Prior to 3.7.0, CSS snippet body containing breaks out of its surrounding tag when renderSnippet() interpolates it via insertAdjacentHTML. A payload like runs arbitrary JavaScript in the renderer. On Electron desktop builds the renderer runs with nodeIntegration:true, so require('child_process') is reachable from the injected handler and the XSS chains to host RCE. Snippets sync via the workspace repository, so an attacker with write access to any synced workspace plants the payload once and it fires on every device that pulls. The bug also bypasses the user's enabledCSS / enabledJS separation. A user who turned enabledJS off was making a deliberate call not to run untrusted JavaScript; the CSS path runs it anyway. This vulnerability is fixed in 3.7.0.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
61
EG Risk 61/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)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 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, 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: 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
31st
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 (9.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-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-26). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

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

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

June 24, 2026

Last Modified

October 25, 2026

Advisory Details (1)

Auto-updated Oct 26, 2026
🔬 Proof of concept available. Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Stored XSS to RCE via CSS-snippet <style> breakout in renderSnippet() · Advisory · siyuan-note/siyuan · GitHub

https://github.com/siyuan-note/siyuan/security/advisories/GHSA-mvjr-vv3c-w4qv

Vendor Advisories for CVE-2026-54067(1)

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

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/siyuan-note/siyuan/kernel—
  • every version up to 0.0.0-20260628153353-2d5d72223df4: fixed in 0.0.0-20260628153353-2d5d72223df4
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 50× 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.

Showing the most recent 100 of 181 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 81 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-10-27 02:18 UTCEG score recompute
  3. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  4. 2026-10-25 23:28 UTCEG score recompute
  5. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  6. 2026-10-25 14:20 UTCEG score recompute
  7. 2026-10-24 17:01 UTCEG score recompute
  8. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  9. 2026-10-23 18:16 UTCEG score recompute
  10. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  11. 2026-10-22 19:13 UTCEG score recompute
  12. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  13. 2026-10-21 20:19 UTCEG score recompute
  14. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  15. 2026-10-20 21:32 UTCEG score recompute
  16. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  17. 2026-10-19 22:46 UTCEG score recompute
  18. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  19. 2026-10-18 22:03 UTCEG score recompute
  20. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  21. 2026-10-18 03:31 UTCEG score recompute
  22. 2026-10-17 22:45 UTCEG score recompute
  23. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  24. 2026-10-16 23:57 UTCEG score recompute
  25. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.5% · 44th percentile
Show 75 more
  1. 2026-10-15 20:51 UTCEG score recompute
  2. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  3. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  4. 2026-10-14 14:57 UTCEG score recompute
  5. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  6. 2026-10-13 14:22 UTCEG score recompute
  7. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  8. 2026-10-12 15:33 UTCEG score recompute
  9. 2026-10-11 19:40 UTCEG score recompute
  10. 2026-10-11 16:55 UTCEG score recompute
  11. 2026-10-11 14:18 UTCEG score recompute
  12. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  13. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  14. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  15. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  17. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  18. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  19. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  20. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  21. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  22. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  23. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  24. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  25. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  26. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  27. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  28. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  29. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  30. 2026-09-23 09:50 UTCEG score recompute
  31. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  32. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  33. 2026-09-18 07:46 UTCEG score recompute
  34. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  35. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  36. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  37. 2026-09-14 01:32 UTCEG score recompute
  38. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  39. 2026-09-12 16:05 UTCEG score recompute
  40. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  41. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  42. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  43. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  44. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  45. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  46. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  47. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  48. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  49. 2026-08-30 19:49 UTCEG score recompute
  50. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  51. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  52. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  53. 2026-08-28 02:58 UTCEG score recompute
  54. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  55. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  56. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  57. 2026-08-24 21:53 UTCEG score recompute
  58. 2026-08-24 13:18 UTCEG score recompute
  59. 2026-08-23 02:26 UTCEG score recompute
  60. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  61. 2026-08-22 00:49 UTCEG score recompute
  62. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  63. 2026-08-20 23:27 UTCEG score recompute
  64. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  65. 2026-08-20 07:13 UTCEG score recompute
  66. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  67. 2026-08-19 01:40 UTCEG score recompute
  68. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  69. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  70. 2026-08-16 18:28 UTCEG score recompute
  71. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  72. 2026-08-16 03:02 UTCEG score recompute
  73. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  74. 2026-08-15 04:55 UTCEG score recompute
  75. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 23rd percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-54067?
CVE-2026-54067 is a critical-severity vulnerability; its CVE record was published on June 24, 2026. SiYuan is an open-source personal knowledge management system. Prior to 3.7.0, CSS snippet body containing </style> breaks out of its surrounding <style> tag when renderSnippet() interpolates it via insertAdjacentHTML. A payload like runs arbitrary JavaScript in the renderer. On Electron desktop…
When was the CVE record for CVE-2026-54067 published?
The CVE record for CVE-2026-54067 was published on June 24, 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 25, 2026; the record at its source may have been updated since.
Is CVE-2026-54067 actively exploited?
CVE-2026-54067 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54067?
CVE-2026-54067 has a CVSS base score of 9.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54067?
A fix for CVE-2026-54067 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54067 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-54067

Explore →

Is Your Infrastructure Affected by CVE-2026-54067?

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

Book a Demo →Browse All CVEs