CVE-2026-41894 | SiYuan up to 3.6.4 url.PathUnescape path traversal
VulDBArchived Apr 24, 2026✓ Full text saved
A vulnerability labeled as critical has been found in SiYuan up to 3.6.4 . The affected element is the function url.PathUnescape . Executing a manipulation can lead to path traversal. This vulnerability is registered as CVE-2026-41894 . It is possible to launch the attack remotely. No exploit is available. The affected component should be upgraded.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-359531 · CVE-2026-41894 · GCVE-0-2026-41894
SIYUAN UP TO 3.6.4 URL.PATHUNESCAPE PATH TRAVERSAL
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
4.1 $0-$5k 0.56+
Summaryinfo
A vulnerability marked as critical has been reported in SiYuan up to 3.6.4. The impacted element is the function url.PathUnescape. The manipulation leads to path traversal. This vulnerability is documented as CVE-2026-41894. The attack can be initiated remotely. There is not any exploit available. It is suggested to upgrade the affected component.
Detailsinfo
A vulnerability was found in SiYuan up to 3.6.4. It has been rated as critical. This issue affects the function url.PathUnescape. The manipulation with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is confidentiality. The summary by CVE is:
SiYuan is an open-source personal knowledge management system. Prior to 3.6.5, the fix for CVE-2026-30869 only added a denylist check (IsSensitivePath) but did not address the root cause — a redundant url.PathUnescape() call in serveExport(). An authenticated attacker can use double URL encoding (%252e%252e) to traverse directories and read arbitrary workspace files including the full SQLite database (siyuan.db), kernel log, and all user documents. This vulnerability is fixed in 3.6.5.
It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-41894 since 04/22/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1006 according to MITRE ATT&CK.
Upgrading to version 3.6.5 eliminates this vulnerability.
Productinfo
Name
SiYuan
Version
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3info
VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Path traversal
CWE: CWE-22
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Upgrade: SiYuan 3.6.5
Timelineinfo
04/22/2026 CVE reserved
04/24/2026 +2 days Advisory disclosed
04/24/2026 +0 days VulDB entry created
04/24/2026 +0 days VulDB entry last update
Sourcesinfo
Advisory: github.com
Status: Confirmed
CVE: CVE-2026-41894 (🔒)
GCVE (CVE): GCVE-0-2026-41894
GCVE (VulDB): GCVE-100-359531
Entryinfo
Created: 04/24/2026 21:23
Changes: 04/24/2026 21:23 (66)
Complete: 🔍
Cache ID: 99:B47:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸