Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-32749: CWE-73: External Control of File Name or Path in siyuan-note siyuan

0
High
VulnerabilityCVE-2026-32749cvecve-2026-32749cwe-73cwe-22
Published: Thu Mar 19 2026 (03/19/2026, 21:07:57 UTC)
Source: CVE Database V5
Vendor/Project: siyuan-note
Product: siyuan

Description

CVE-2026-32749 is a high-severity vulnerability in SiYuan personal knowledge management system versions 3. 6. 0 and below. It involves improper sanitization of file paths in two API endpoints that handle uploaded archives, allowing an admin user to write files to arbitrary locations outside the intended temporary directory. This flaw can lead to remote code execution (RCE) by overwriting critical system or application files. In Docker containers running as root, exploitation results in full container compromise. The vulnerability does not require user interaction but does require admin privileges. It has been fixed in version 3. 6. 1.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/27/2026, 19:33:27 UTC

Technical Analysis

CVE-2026-32749 is a vulnerability classified under CWE-73 (External Control of File Name or Path) and CWE-22 (Path Traversal) affecting SiYuan, a personal knowledge management system. Versions 3.6.0 and earlier contain a flaw in the POST /api/import/importSY and POST /api/import/importZipMd endpoints, which accept uploaded archive files. These endpoints derive the file write path directly from the multipart filename field without proper sanitization or validation. This allows an authenticated admin user to craft filenames containing path traversal sequences or absolute paths, enabling writing files outside the designated temporary directory. Such arbitrary file writes can overwrite critical workspace or application files, potentially leading to remote code execution (RCE). The risk is especially severe in Docker container deployments running as root, a common default configuration, where successful exploitation grants full container compromise. The vulnerability has a CVSS 3.1 base score of 7.6, indicating high severity, with an attack vector over the network, low attack complexity, requiring privileges (admin), no user interaction, and scope change. No known exploits are reported in the wild yet. The issue was fixed in SiYuan version 3.6.1 by implementing proper path sanitization and validation to prevent directory traversal and arbitrary file writes.

Potential Impact

The vulnerability allows an authenticated admin user to write files to arbitrary locations on the host system, which can lead to overwriting critical application or workspace files, causing data loss or corruption. More critically, it enables remote code execution by placing malicious files in system or application paths, potentially allowing attackers to execute arbitrary commands. In containerized environments, especially Docker containers running as root, exploitation can lead to full container compromise, allowing attackers to control the container environment, escalate privileges, and potentially pivot to the host system or other network resources. This poses significant risks to confidentiality, integrity, and availability of organizational data and services. Organizations relying on SiYuan for knowledge management, especially those deploying it in containerized or production environments, face risks of operational disruption, data destruction, and unauthorized access.

Mitigation Recommendations

Organizations should immediately upgrade SiYuan to version 3.6.1 or later, where the vulnerability is patched. Until upgrading, restrict admin access to trusted personnel only and monitor for suspicious activity related to file uploads. Implement network segmentation and container security best practices, such as running containers with least privilege (non-root users) to limit the impact of potential exploitation. Employ file integrity monitoring to detect unauthorized changes to critical files. Additionally, review and harden API access controls to ensure only authorized users can perform import operations. Consider deploying Web Application Firewalls (WAFs) with rules to detect and block path traversal attempts. Regularly audit container configurations and logs for signs of compromise. Finally, maintain up-to-date backups of workspace and application data to enable recovery in case of data destruction.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-13T18:53:03.531Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69bc698ee32a4fbe5ffae0a4

Added to database: 3/19/2026, 9:24:30 PM

Last enriched: 3/27/2026, 7:33:27 PM

Last updated: 5/2/2026, 7:40:25 AM

Views: 116

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses