SiYuan: path traversal via /export/temp/ short-circuit branch (incomplete fix for the export-disclosure hardening, GHSA-6865-qjcf-286f)

Exploitation

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

CVSS

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

EPSS

• CVE-2026-65607: 0.59% estimated exploitation activity in the next 30 days; percentile 48.06 (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 SiYuan's /export/ file handler was hardened against export disclosure (issue #12213) by adding an IsSubPath(exportBaseDir, fullPath) check and an IsSensitivePath() check in commit bb481e1. These guards were added only to the main branch of the handler. The handler begins with a short-circuit branch: This branch joins the broader util.TempDir with the raw, percent-decoded request path and serves it with neither IsSubPath nor IsSensitivePath. An authenticated request to /export/temp/%2e%2e/.../etc/passwd traverses out of TempDir and reads arbitrary files - exactly the sensitive-file disclosure the patch intended to prevent. Present in the latest master. Affected - From commit bb481e1 (the hardening) through the latest master. - Requires SiYuan access authorization (model.CheckAuth) - but the patch's stated goal is to deny sensitive-file export even to authorized callers. Root cause kernel/server/serve.go serveExport(): the main branch has IsSubPath + IsSensitivePath; the…

Published by the source

3 Sep 2026, 14:56 UTC

Last modified by the source

10 Sep 2026, 15:25 UTC

Source last checked

26 Oct 2026, 15:29 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-gw25-m53r-qh88

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6365

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-gw25-m53r-qh88

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

# Patch Next advisory brief: CVE-2026-65607

Advisory: SiYuan: path traversal via /export/temp/ short-circuit branch (incomplete fix for the export-disclosure hardening, GHSA-6865-qjcf-286f)
IDs: CVE-2026-65607, GHSA-gw25-m53r-qh88
Record: https://patchnext.com/advisories/cve-2026-65607 (revision 3, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/siyuan-note/siyuan/kernel 0.0.0-20260510110132-b763d787d1f2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/siyuan-note/siyuan/kernel: affected < 0.0.0-20260510110132-b763d787d1f2; fixed in 0.0.0-20260510110132-b763d787d1f2

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

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## 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://osv.dev/vulnerability/GHSA-gw25-m53r-qh88 (OSV record GHSA-gw25-m53r-qh88 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260510110132-b763d787d1f2 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6365 (OSV record GO-2026-6365 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260510110132-b763d787d1f2 (fixed))
- Verified: https://github.com/advisories/GHSA-gw25-m53r-qh88 (GitHub-reviewed advisory GHSA-gw25-m53r-qh88 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260510110132-b763d787d1f2)

Commands are suggestions: review each one before running it.