cve.bz

CVE-2026-40318 b3log siyuan: Path Traversal: '../filedir'

8.5 highEPSS 0.3%Fix available

High (8.5) in b3log siyuan. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/siyuan-note/siyuan/kernel 3.6.40.0.0-20260407035653-2f416e5253f1.

On this page
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.

Severity

CVSS 3.1

8.5 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 22nd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-04-18. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-24 Path Traversal: '../filedir'
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-40318 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-40318?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-40318?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-40318 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
b3log:siyuanbefore 3.6.4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-vw86-c94w-v3x4Gogithub.com/siyuan-note/siyuan/kernel<3.6.40.0.0-20260407035653-2f416e5253f13.6.40.0.0-20260407035653-2f416e5253f1
GO-2026-5679Gogithub.com/siyuan-note/siyuan/kernelall versionsno fix published

Linux distributions

DistributionReleasePackageFixed inAdvisory
openSUSELeap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE.

References

Check your stackJSON