SiYuan: ZipSlip -> Arbitrary File Overwrite -> RCE

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.8 · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS

• CVE-2025-67488: 0.44% estimated exploitation activity in the next 30 days; percentile 38.20 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Function importZipMd is vulnerable to ZipSlip which allows an authenticated user to overwrite files on the system. Details An authenticated user with access to the import functionality in notes is able to overwrite any file on the system, the vulnerable function is importZipMd, this can escalate to full code execution under some circumstances, for example using the official docker image it is possible to overwrite entrypoint.sh and after a container restart it will execute the changed code causing remote code execution. PoC Code used to generate the ZipSlip: Impact The exploit is possible only if the attacker has access to import functionality. It's possible to achieve code execution and some persistence within the container

Published by the source

9 Dec 2025, 17:18 UTC

Last modified by the source

9 Dec 2025, 21:37 UTC

Source last checked

26 Oct 2026, 15:13 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-gqfv-g4v7-m366

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-67488

Advisory: SiYuan: ZipSlip -> Arbitrary File Overwrite -> RCE
IDs: CVE-2025-67488, GHSA-gqfv-g4v7-m366
Record: https://patchnext.com/advisories/cve-2025-67488 (revision 1, source checked 26 Oct 2026, 15:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/siyuan-note/siyuan/kernel: affected <= 0.0.0-20251202123337-6ef83b42c7ce

## Suggested inspection (read-only)
- Go github.com/siyuan-note/siyuan/kernel: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/siyuan-note/siyuan/kernel.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-gqfv-g4v7-m366 (GitHub-reviewed advisory GHSA-gqfv-g4v7-m366 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <=0.0.0-20251202123337-6ef83b42c7ce)

Commands are suggestions: review each one before running it.