CVE-2026-130683 json
SiYuan before 3.8.10 Path Traversal via /api/file/copyFile Deny-List Bypass
published 18d ago modified 19m ago also GHSA-4xfj-946m-258h
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository siyuan-note/siyuan. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 9.3
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
SiYuan before 3.8.10 uses an incomplete deny-list in IsSensitivePath that omits shell-initialization files such as .zshenv and .bash_profile, as well as ~/.local. Authenticated administrators can call /api/file/copyFile with an absolute destination outside the workspace to write payloads there, which execute as the user on the next shell or login.
Patch / fix
- siyuan-note siyuan 3.8.10
Is CVE-2026-130683 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 9.3 | CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H |
| CNA | 3.1 | 8.2 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H |
| NVD | 3.1 | 8.2 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H |
Affected products
- siyuan-note siyuan
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/siyuan-note/siyuan/security/advisories/GHSA-4xfj-946m-258h
vendor-advisory, advisory
Sources
- CVE List CVE-2026-130683
- NVD CVE-2026-130683
- Maintainer advisory GHSA-4xfj-946m-258h
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.
The maintainers of siyuan-note/siyuan published their own advisory on GitHub. Reviewed sources take precedence over it.