SiYuan is a personal knowledge management system. In versions 3.6.0 and below, POST /api/import/importSY and POST /api/import/importZipMd write uploaded archives to a path derived from the multipart filename field without sanitization, allowing an admin to write files to arbitrary locations outside the temp directory - including system paths that enable RCE. This can lead to aata destruction by overwriting workspace or application files, and for Docker containers running as root (common default), this grants full container compromise. This issue has been fixed in version 3.6.1.
CVE-2026-32749
This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory enrichment pending alignment with NVD CVSS.
- 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
- 9.1
- EG Score
- 9.1(low)
- EG Risk
- 45(Track)EG Risk 45/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 computedSeverity91% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
March 19, 2026
Last Modified
June 17, 2026
Advisory Details (3)
Auto-updated Jul 27, 2026importSY/importZipMd: path traversal via multipart filename enables arbitrary file write · Advisory · siyuan-note/siyuan · GitHub
https://github.com/siyuan-note/siyuan/security/advisories/GHSA-qvvf-q994-x79vImprove details
Patch available: siyuan-note/siyuan v3.6.1
https://github.com/siyuan-note/siyuan/releases/tag/v3.6.1commit 5ee00907f0b0 (siyuan-note/siyuan)
Fix landed in siyuan-note/siyuan commit 5ee00907f0b0 — awaiting tagged release
https://github.com/siyuan-note/siyuan/commit/5ee00907f0b0c4aca748ce21ef1977bb98178e14Patch 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 3× in last 7d / 3× 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: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-25539NVD 7.2EG 9.1CRITICAL
- CVE-2025-21609EG 9.1CRITICAL
- CVE-2026-45375EG 9.0CRITICAL
- CVE-2026-32751EG 9.0CRITICAL
Frequently asked(4)
What is CVE-2026-32749?
When was CVE-2026-32749 disclosed?
What is the CVSS score of CVE-2026-32749?
How do I remediate CVE-2026-32749?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-32749
Is Your Infrastructure Affected by CVE-2026-32749?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.