SiYuan: getUniqueFilename passes an unvalidated client-supplied path to the filesystem, giving anonymous readers an existence oracle over the entire host filesystem

Exploitation

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

CVSS

5.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

EPSS

• CVE-2026-73605: 0.33% estimated exploitation activity in the next 30 days; percentile 25.60 (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 /api/file/getUniqueFilename takes a path from the request body and passes it to a filesystem existence check with no validation, confinement or authorization. The response distinguishes paths that exist from paths that do not, so an anonymous reader in publish mode can probe arbitrary locations on the host, one request per probe. Files and directories both work. Every neighbouring file route either requires an administrator or confines the path first. Details Route. kernel/api/router.go:289 on master, :292 on the development branch, CheckAuth only. Handler, kernel/api/file.go:84, in full: The argument binder does no path handling. util.BindJsonArg (kernel/util/net.go:365) takes two booleans, required (the key must be present) and rejectEmpty (the value must be non-empty). That is its entire contract. There is no filepath.Clean, no workspace join, no traversal check. An absolute path outside the workspace reaches gulu.File.IsExist unmodified. The oracle. util/file.go:67: Input…

Published by the source

1 Oct 2026, 15:46 UTC

Last modified by the source

7 Oct 2026, 17:45 UTC

Source last checked

26 Oct 2026, 15:29 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-hf8h-97gm-4x2p

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6626

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-hf8h-97gm-4x2p

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

# Patch Next advisory brief: CVE-2026-73605

Advisory: SiYuan: getUniqueFilename passes an unvalidated client-supplied path to the filesystem, giving anonymous readers an existence oracle over the entire host filesystem
IDs: CVE-2026-73605, GHSA-hf8h-97gm-4x2p
Record: https://patchnext.com/advisories/cve-2026-73605 (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 5.8)
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-20260812083335-251596fc0de2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/siyuan-note/siyuan/kernel: affected < 0.0.0-20260812083335-251596fc0de2; fixed in 0.0.0-20260812083335-251596fc0de2

## 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/GO-2026-6626 (OSV record GO-2026-6626 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260812083335-251596fc0de2 (fixed))
- Verified: https://osv.dev/vulnerability/GHSA-hf8h-97gm-4x2p (OSV record GHSA-hf8h-97gm-4x2p lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260812083335-251596fc0de2 (fixed))
- Verified: https://github.com/advisories/GHSA-hf8h-97gm-4x2p (GitHub-reviewed advisory GHSA-hf8h-97gm-4x2p lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260812083335-251596fc0de2)

Commands are suggestions: review each one before running it.