SiYuan: Absolute filesystem path and OS username disclosure via resolveAssetPath

Exploitation

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

CVSS

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

EPSS

• CVE-2026-72802: 0.30% estimated exploitation activity in the next 30 days; percentile 22.35 (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.

CVE: This vulnerability corresponds to CVE-2026-72802. Summary POST /api/asset/resolveAssetPath returns the resolved absolute filesystem path of an asset, unmodified. The route is CheckAuth-only, so it is reachable by the publish RoleReader token and by the anonymous account when Publish.Auth.Enable is false. An anonymous reader who knows any asset's relative path trivially harvested from an <img src="assets/…" in any published document receives the server's absolute workspace path, disclosing the operating-system username and the installation layout. Details GetAssetAbsPathInBox(path, "") resolves under util.DataDir / util.WorkspaceDir, producing a full host path such as C:\Users\<username\SiYuan\data\assets\foo.png or /home/<user/…. The handler returns it directly with no redaction and no publish-scope check. This is data the project already treats as sensitive. getConf explicitly zeroes System.WorkspaceDir, AppDir, ConfDir, DataDir, and HomeDir when util.IsBrowserRequest(c), a…

Published by the source

3 Sep 2026, 23:00 UTC

Last modified by the source

10 Sep 2026, 15:15 UTC

Source last checked

26 Oct 2026, 15:29 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-jv8v-xq2h-657v

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6398

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-jv8v-xq2h-657v

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

# Patch Next advisory brief: CVE-2026-72802

Advisory: SiYuan: Absolute filesystem path and OS username disclosure via resolveAssetPath
IDs: CVE-2026-72802, GHSA-jv8v-xq2h-657v
Record: https://patchnext.com/advisories/cve-2026-72802 (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.3)
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-20260724095509-eee3410aa131. A vendor fix does not mean a deployment is fixed.

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

## 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-jv8v-xq2h-657v (OSV record GHSA-jv8v-xq2h-657v lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260724095509-eee3410aa131 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6398 (OSV record GO-2026-6398 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260724095509-eee3410aa131 (fixed))
- Verified: https://github.com/advisories/GHSA-jv8v-xq2h-657v (GitHub-reviewed advisory GHSA-jv8v-xq2h-657v lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260724095509-eee3410aa131)

Commands are suggestions: review each one before running it.