CVE-2026-40318
B3Log Siyuan ≤ 3.6.4
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:HSummary
CVE-2026-40318 is a high-severity Path Traversal: '../filedir' (CWE-24) vulnerability in B3Log Siyuan. Its CVSS base score is 8.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-40318 is a path traversal vulnerability (CWE-24) in SiYuan, an open-source personal knowledge management system. The issue affects versions 3.6.3 and prior, where the /api/av/removeUnusedAttributeView endpoint constructs filesystem paths using a user-controlled id parameter without validation or path boundary checks. This allows attackers to inject traversal sequences like ../ to access and delete files outside the intended directory, targeting arbitrary .json files such as global configuration files and workspace metadata. The vulnerability carries a CVSS v3.1 base score of 8.5 (AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H).
An authenticated attacker with low privileges (PR:L) can exploit this over the network with low complexity and no user interaction required. By crafting a malicious id parameter in requests to the endpoint, they can traverse directories and delete critical .json files, potentially disrupting system configuration, workspace data, and overall availability, while achieving low integrity impact through unauthorized deletions.
The vulnerability has been addressed in SiYuan version 3.6.4. Security practitioners should upgrade to this patched release, as detailed in the project's release notes (https://github.com/siyuan-note/siyuan/releases/tag/v3.6.4) and GitHub Security Advisory (https://github.com/siyuan-note/siyuan/security/advisories/GHSA-vw86-c94w-v3x4).
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-23328
Vulnerability Data
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…
more
../ 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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Input validation directly neutralizes '../' sequences in externally-supplied pathnames before they are resolved.
Enforced access authorizations can limit the damage even when path traversal succeeds.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input validation and path sanitization that prevent ../ traversal.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure coding standards require neutralizing ../ sequences and canonicalizing paths before file operations.
Security testing in development catches path-traversal flaws before release.
Secure SDLC mandates input validation and path canonicalization that directly block ../ traversal.
Application security requirements explicitly call for controls against path traversal in file-handling functions.
Secure architecture principles reduce attack surface but do not prescribe the specific coding fix.
Information access restriction limits which files can be reached, mitigating impact of traversal.