SiYuan kernel before v3.7.4 contains a path traversal vulnerability in the database_clean MCP tool. The tool performs only an empty-string check on the id parameter before passing it to RemoveUnusedAttributeView (kernel/model/attribute_view.go), which builds a filesystem path via filepath.Join without validating that id matches SiYuan's node-ID format. An authenticated MCP client can supply path traversal sequences in id to cause the kernel to copy an arbitrary file readable by the process into SiYuan's history directory (arbitrary file read) and then delete the original file (arbitrary file deletion). The corresponding HTTP API handler was hardened in GHSA-7hm9-v7vf-7g4w, but this MCP caller was not.
CVE-2026-74798
Score 8.7 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-17. a secondary CVSS source baseline 8.7; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.7
- EG Score
- 8.7(high)
- EG Risk
- 55(Track*)EG Risk 55/100SSVC: Track*
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity87% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 30%
- KEV
- Not listed
Published
August 17, 2026
Last Modified
August 18, 2026
Advisory Details (2)
Auto-updated Aug 17, 2026SiYuan kernel Path Traversal via database_clean MCP tool | Advisories | VulnCheck
https://www.vulncheck.com/advisories/siyuan-kernel-path-traversal-via-database-clean-mcp-toolPath Traversal in MCP tool database_clean (RemoveUnusedAttributeView) leads to Arbitrary File Read (via history copy) and Arbitrary File Deletion, missed by the recent GHSA-7hm9-v7vf-7g4w fix · Advisory · siyuan-note/siyuan · GitHub
https://github.com/siyuan-note/siyuan/security/advisories/GHSA-43jx-gxq4-jpjcVendor Advisories for CVE-2026-74798(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 22× in last 7d / 22× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-21 00:28 UTCEG score recompute
- 2026-08-21 00:28 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 13:05 UTCGHSA enrichment
- 2026-08-20 01:32 UTCEG score recompute
- 2026-08-20 01:32 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 14:08 UTCGHSA enrichment
- 2026-08-19 02:45 UTCEG score recompute
- 2026-08-19 02:45 UTCGHSA enrichment
- 2026-08-18 15:18 UTCEG score recompute
- 2026-08-18 15:18 UTCGHSA enrichment
- 2026-08-18 14:51 UTCEG score recompute
- 2026-08-18 14:51 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 10:30 UTCGHSA enrichment
- 2026-08-17 23:06 UTCEG score recompute
- 2026-08-17 23:06 UTCGHSA enrichment
- 2026-08-17 11:42 UTCEG score recompute
- 2026-08-17 11:13 UTCEG score recompute
- 2026-08-17 11:12 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-74798?
When was CVE-2026-74798 disclosed?
Is CVE-2026-74798 actively exploited?
What is the CVSS score of CVE-2026-74798?
How do I remediate CVE-2026-74798?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-74798
Is Your Infrastructure Affected by CVE-2026-74798?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.