CVE-2026-44670: siyuan · Cross-site Scripting
Affects siyuanSource CVE Database V5
Not known to be exploited · CVSS 9.4 Critical : upgrade to 3.7.0 as a priority.
Data as of 16 Nov 2026, 20:25 UTC
Contested
Critical score, yet low EPSS after six months- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.7.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:HExploitation evidence
Disclosed: evidence found.
CVE published 14 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade siyuan and siyuan-note/siyuan to 3.7.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| siyuan-notesiyuan | Affected
| Fixed in
|
GitHubsiyuan-note/siyuanpkg:github/siyuan-note/siyuanOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in SiYuan version 3.7.0. Users should upgrade to version 3.7.0 or later to remediate this issue. No other official remediation or temporary fixes are indicated. Patch status is not explicitly stated in vendor advisories but the fix is included in the 3.7.0 release. Until upgrading, avoid processing untrusted input as Attribute View names.
Description
CVE-2026-44670 is a critical cross-site scripting (XSS) vulnerability in the SiYuan personal knowledge management system versions prior to 3.7.0. The issue arises because Attribute View names are stored and rendered without HTML escaping, allowing malicious input to be injected into the HTML sent to clients. Due to insecure Electron app settings (nodeIntegration:true, contextIsolation:false, webSecurity:false), this HTML injection can escalate to Node.js code execution in the renderer process. This vulnerability is fixed in version 3.7.0.