CVE-2026-118680: SiYuan 3.8.7 through 3.8.8 fails to normalize Windows GLOBALROOT device-namespace aliases, bypassing
Affects siyuanSource GCVE Database
Not known to be exploited · CVSS 5.9 Medium.
Data as of 28 Oct 2026, 22:14 UTC
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Affected software
| Product | 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
Until a fix is available, restrict access to the importStdMd function and avoid using GLOBALROOT-prefixed paths. Monitor for vendor updates and apply official patches once released.
Description
SiYuan versions 3.8.7 through 3.8.8 have a vulnerability where Windows GLOBALROOT device-namespace aliases are not normalized, allowing attackers to bypass the IsSensitivePath denylist. This flaw enables attackers with appropriate privileges to invoke importStdMd with a specially crafted GLOBALROOT-prefixed path, resulting in unauthorized copying of sensitive files such as the API token and TLS private key into a publicly accessible directory.