SiYuan Vulnerable to Arbitrary File Read in Desktop Publish Service

Exploitation

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

CVSS

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

EPSS

• CVE-2026-32938: 0.42% estimated exploitation activity in the next 30 days; percentile 36.48 (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 In SiYuan, /api/lute/html2BlockDOM on the desktop copies local files pointed to by file:// links in pasted HTML into the workspace assets directory without validating paths against a sensitive-path list. Together with GET /assets/path, which only requires authentication, a publish-service visitor can cause the desktop kernel to copy any readable sensitive file and then read it via GET, leading to exfiltration of sensitive files. Details 1. Arbitrary local files copied into workspace - Endpoint: POST /api/lute/html2BlockDOM, protected only by model.CheckAuth; publish read-only role is not restricted. - Behavior: On desktop (util.ContainerStd == model.Conf.System.Container), local absolute paths from <a href="file://..." in the HTML are copied to {DataDir}/assets/. - Missing check: The code does not call util.IsSensitivePath(localPath) before copying, so any readable file (e.g. /etc/passwd, ~/.ssh/idrsa) can be copied into assets. 2. Direct access to assets via GET - Endpoint:…

Published by the source

17 Mar 2026, 14:07 UTC

Last modified by the source

20 Mar 2026, 21:21 UTC

Source last checked

26 Oct 2026, 15:18 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-fq2j-j8hc-8vw8

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

# Patch Next advisory brief: CVE-2026-32938

Advisory: SiYuan Vulnerable to Arbitrary File Read in Desktop Publish Service
IDs: CVE-2026-32938, GHSA-fq2j-j8hc-8vw8
Record: https://patchnext.com/advisories/cve-2026-32938 (revision 1, source checked 26 Oct 2026, 15:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.9)
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-20260313024916-fd6526133bb3

## 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-fq2j-j8hc-8vw8 (GitHub-reviewed advisory GHSA-fq2j-j8hc-8vw8 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <=0.0.0-20260313024916-fd6526133bb3)

Commands are suggestions: review each one before running it.