Skip to content
Fencer Intel
high 8.5

CVE-2026-40318 json

SiYuan: Publish Reader Path Traversal Delete via `removeUnusedAttributeView`

published 6mo ago modified last mo. also EUVD-2026-23328 , GHSA-vw86-c94w-v3x4 , GO-2026-5679

cvss
8.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 21%
public exploits
0
none known

Summary

SiYuan is an open-source personal knowledge management system. In versions 3.6.3 and prior, the /api/av/removeUnusedAttributeView endpoint constructs a filesystem path using the user-controlled id parameter without validation or path boundary enforcement. An attacker can inject path traversal sequences such as ../ into the id value to escape the intended directory and delete arbitrary .json files on the server, including global configuration files and workspace metadata. This issue has been fixed in version 3.6.4.

Patch / fix

  • go github.com/siyuan-note/siyuan/kernel 3.6.40.0.0-20260407035653-2f416e5253f1
  • b3log siyuan 3.6.4
  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

Is CVE-2026-40318 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
6mo ago

Exploit prediction

0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 8.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H
GitHub 3.1 8.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H

Affected packages

ecosystem package affected fixed in
go github.com/siyuan-note/siyuan/kernel
<3.6.40.0.0-20260407035653-2f416e5253f1
all versions
3.6.40.0.0-20260407035653-2f416e5253f1

Affected products

  • siyuan-note siyuan

Classification

Weakness
  • CWE-24 Path Traversal: '../filedir'

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.