CVE-2026-44670

CRITICALNVD 9.49.4—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.4 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 60% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.4Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

SiYuan is an open-source personal knowledge management system. Prior to 3.7.0, the kernel stores Attribute View (AV / database) names without any HTML escape, then a render template uses raw strings.ReplaceAll(tpl, "${avName}", nodeAvName) to embed the name in HTML before pushing to all clients via WebSocket. Three independent client paths (render.ts:120 → outerHTML, Title.ts:401 → innerHTML, transaction.ts:559 → innerHTML) consume the value without escaping. Because the main BrowserWindow runs nodeIntegration:true, contextIsolation:false, webSecurity:false (app/electron/main.js:407-411), HTML injection in the renderer becomes Node.js code execution. This vulnerability is fixed in 3.7.0.

CVSS v3
9.4
EG Score
9.4(medium)
EPSS
39.8%
KEV
Not listed

Published

May 14, 2026

Last Modified

May 15, 2026

Advisory Details (1)

Auto-updated May 14, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Stored XSS via Attribute View name to Electron renderer RCE in SiYuan · Advisory · siyuan-note/siyuan · GitHub

https://github.com/siyuan-note/siyuan/security/advisories/GHSA-2h64-c999-c9r6

Vendor Advisories for CVE-2026-44670(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 rangeFixed inDependents
github.com/siyuan-note/siyuan/kernel—0.0.0-20260512140701-d7b77d945e0d—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 70× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 173 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-44670?
CVE-2026-44670 is a critical vulnerability published on May 14, 2026. SiYuan is an open-source personal knowledge management system. Prior to 3.7.0, the kernel stores Attribute View (AV / database) names without any HTML escape, then a render template uses raw strings.ReplaceAll(tpl, "${avName}", nodeAvName) to embed the name in HTML before pushing to all clients via…
When was CVE-2026-44670 disclosed?
CVE-2026-44670 was first published in the National Vulnerability Database on May 14, 2026, with the most recent update on May 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44670 actively exploited?
CVE-2026-44670 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 39.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44670?
CVE-2026-44670 has a CVSS v3 base score of 9.4 (NVD).
How do I remediate CVE-2026-44670?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44670, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44670

Explore →

Is Your Infrastructure Affected by CVE-2026-44670?

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

Start Free Scan →Browse All CVEs