SiYuan is a personal knowledge management system. Prior to version 3.6.2, the Siyuan kernel exposes an unauthenticated file-serving endpoint under /appearance/*filepath. Due to improper path sanitization, attackers can perform directory traversal and read arbitrary files accessible to the server process. Authentication checks explicitly exclude this endpoint, allowing exploitation without valid credentials. Version 3.6.2 fixes this issue.
CVE-2026-33476
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-03-20. the CNA's CVSS baseline 7.5; 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
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 65(Attend)EG Risk 65/100SSVC: Attend
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 computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 3%
- EPSS %ILE
- 87%
- KEV
- Not listed
Published
March 20, 2026
Last Modified
June 17, 2026
References (3)
- security-advisories@githubhttps://github.com/siyuan-note/siyuan/commit/009bb598b3beccc972aa5f1ed88b3b224326bf2a
- security-advisories@githubhttps://github.com/siyuan-note/siyuan/security/advisories/GHSA-hhgj-gg9h-rjp7
- 134c704f-9b21-4f2e-91b3-4a467353bcc0https://github.com/siyuan-note/siyuan/security/advisories/GHSA-hhgj-gg9h-rjp7
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| go | github.com/siyuan-note/siyuan/kernel | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× 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-07-27 14:13 UTCEPSS rescore
- 2026-07-27 12:51 UTCEG score recompute
- 2026-07-27 12:51 UTCGHSA enrichment
- 2026-07-27 12:50 UTCOSV refresh
Publicly available exploits
(1 reference)Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- Nucleihttp/cves/2026/CVE-2026-33476.yamlFirst seen Jan 1, 2026
SiYuan <= v3.6.1 - Path Traversal
Open source ↗
Related CVEs(same product + same CWE)
Same product
10 showngo:github.com/siyuan-note/siyuan/kernel
- CVE-2026-32938NVD 6.5EG 9.9CRITICAL
- CVE-2026-33670NVD 7.5EG 9.8CRITICAL
- CVE-2026-33669NVD 7.5EG 9.8CRITICAL
- CVE-2026-32767EG 9.8CRITICAL
- CVE-2024-55660EG 9.8CRITICAL
- CVE-2026-44588EG 9.4CRITICAL
- CVE-2026-32749EG 9.1CRITICAL
- CVE-2026-25539NVD 7.2EG 9.1CRITICAL
- CVE-2025-21609EG 9.1CRITICAL
- CVE-2026-45375EG 9.0CRITICAL
Frequently asked(5)
What is CVE-2026-33476?
When was CVE-2026-33476 disclosed?
Is CVE-2026-33476 actively exploited?
What is the CVSS score of CVE-2026-33476?
How do I remediate CVE-2026-33476?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-33476
Is Your Infrastructure Affected by CVE-2026-33476?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.