SiYuan is a personal knowledge management system. In versions 3.6.0 and below, the globalCopyFiles API eads source files using filepath.Abs() with no workspace boundary check, relying solely on util.IsSensitivePath() whose blocklist omits /proc/, /run/secrets/, and home directory dotfiles. An admin can copy /proc/1/environ or Docker secrets into the workspace and read them via the standard file API. An admin can exfiltrate any file readable by the SiYuan process that falls outside the incomplete blocklist. In containerized deployments this includes all injected secrets and environment variables - a common pattern for passing credentials to containers. The exfiltrated files are then accessible via the standard workspace file API and persist until manually deleted. This issue has been fixed in version 3.6.1.
CVE-2026-32747
Score 6.8 from GitHub Security Advisory published 2026-03-16. NVD baseline CVSS 4.9; sources differ by 1.9.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.9
- EG Score
- 6.8(medium)
- EG Risk
- 35(Track)EG Risk 35/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 computedSeverity68% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 34%
- KEV
- Not listed
Published
March 19, 2026
Last Modified
June 17, 2026
References (4)
- security-advisories@githubhttps://github.com/siyuan-note/siyuan/commit/9914fd1d39e5f0a8dcc9fb587e1c0b46f31490a1
- security-advisories@githubhttps://github.com/siyuan-note/siyuan/releases/tag/v3.6.1
- security-advisories@githubhttps://github.com/siyuan-note/siyuan/security/advisories/GHSA-h5vh-m7fg-w5h6
- 134c704f-9b21-4f2e-91b3-4a467353bcc0https://github.com/siyuan-note/siyuan/security/advisories/GHSA-h5vh-m7fg-w5h6
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 6× in last 7d / 6× 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-01 04:16 UTCEPSS rescore
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-27 14:38 UTCEG score recompute
- 2026-07-27 14:38 UTCGHSA enrichment
- 2026-07-27 14:27 UTCOSV refresh
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-32747?
When was CVE-2026-32747 disclosed?
Is CVE-2026-32747 actively exploited?
What is the CVSS score of CVE-2026-32747?
How do I remediate CVE-2026-32747?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-32747
Is Your Infrastructure Affected by CVE-2026-32747?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.