# CVE-2025-67488: SiYuan: ZipSlip -> Arbitrary File Overwrite -> RCE > An authenticated user can exploit a ZipSlip vulnerability in SiYuan to overwrite arbitrary files, potentially leading to remote code execution. - **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 9 Dec 2025 - **Updated:** 9 Dec 2025 - **Also known as:** GHSA-gqfv-g4v7-m366, GO-2025-4221 ## What is CVE-2025-67488? CVE-2025-67488 is a high-severity path traversal vulnerability in B3log Siyuan, published on 9 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description SiYuan is self-hosted, open source personal knowledge management software. Versions 0.0.0-20251202123337-6ef83b42c7ce and below contain function importZipMd which is vulnerable to ZipSlips, allowing an authenticated user to overwrite files on the system. An authenticated user with access to the import functionality in notes is able to overwrite any file on the system, and can escalate to full code execution under some circumstances. A fix is planned for version 3.5.0. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2025-67488? 3 open source packages ship an affected version, including github.com/siyuan-note/siyuan/kernel. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/siyuan-note/siyuan/kernel` | Go | All versions | None | | `github.com/siyuan-note/siyuan/kernel` | Go | All versions to 0.0.0-20251202123337-6ef83b42c7ce | None | | `github.com/siyuan-note/siyuan/kernel` | Go | All versions to 0.0.0-20251202123337-6ef83b42c7ce | None | Products: B3log Siyuan. ## How do I fix CVE-2025-67488? Upgrade to a fixed version. ## Is CVE-2025-67488 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-67488 exists. ## Other vulnerabilities in B3log Siyuan - [CVE-2026-32938](https://insights.sbomify.com/CVE-2026-32938/): SiYuan has an Arbitrary File Read in its Desktop Publish Service (critical 9.9) - [CVE-2026-33669](https://insights.sbomify.com/CVE-2026-33669/): SiYuan has Arbitrary Document Reading within the Publishing Service (critical 9.8) - [CVE-2026-33670](https://insights.sbomify.com/CVE-2026-33670/): SiYuan has directory traversal within its publishing service (critical 9.8) - [CVE-2026-32767](https://insights.sbomify.com/CVE-2026-32767/): SiYuan: Authorization Bypass Allows Arbitrary SQL Execution via Search API (critical 9.8) - [CVE-2024-53504](https://insights.sbomify.com/CVE-2024-53504/): SQL injection in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-67488 and fix it if it is affected. What it is: CVE-2025-67488 is a high-severity path traversal vulnerability in B3log Siyuan, published on 9 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-67488 exists. Affected packages and fixed versions: - github.com/siyuan-note/siyuan/kernel (Go): affected all versions; no fix listed - github.com/siyuan-note/siyuan/kernel (Go): affected all versions up to 0.0.0-20251202123337-6ef83b42c7ce; no fix listed - github.com/siyuan-note/siyuan/kernel (Go): affected all versions up to 0.0.0-20251202123337-6ef83b42c7ce; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-67488/ (Markdown: https://insights.sbomify.com/CVE-2025-67488/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-67488 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-67488 - OSV: https://osv.dev/vulnerability/CVE-2025-67488 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-67488/ Summaries are generated and may contain mistakes; the official description above is the record.