Skip to main content
CVE-2026-116171VulnerabilityPublished 10/25/2026

CVE-2026-116171: siyuan · Path Traversal

Affects siyuan-note siyuanSource CVE Database V5

0

Not known to be exploited · CVSS 8.7 High.

Data as of 10/25/2026, 17:13:39 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
siyuan-notesiyuanAffected
  • >=3.5.4 <3.8.7
Fixed in
  • 3.8.7
GitHubsiyuan-note/siyuanpkg:github/siyuan-note/siyuanOther threatsAffected
  • >=3.5.4 <3.8.7
Fixed in
  • 3.8.7

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 API access to trusted users only and monitor for suspicious activity related to the /api/import/importStdMd endpoint.

Description

SiYuan 3.5.4 before 3.8.7 on Windows contains a sensitive-path denylist bypass in IsSensitivePath because the Windows extended-length prefix (\\?\) survives filepath.Clean and matches no forbidden prefix. Authenticated API callers can prepend the prefix to localPath in /api/import/importStdMd to copy workspace conf files, including the API token and TLS private keys, into assets served to unauthenticated clients.

Impact

An attacker with authenticated API access can bypass pathname restrictions to access and expose sensitive files including API tokens and TLS private keys. This could lead to unauthorized access and compromise of the system or data confidentiality. The vulnerability has a high severity score (CVSS 8.7) reflecting the potential impact.

References

Community reviews

Loading reviews…