Advisory record · GHSA-fq2j-j8hc-8vw8

SiYuan Vulnerable to Arbitrary File Read in Desktop Publish Service

CVSS 9.9 CriticalCriticalEPSS 0.0047 · 41st percentile

Critical, because:

  • CVSS score 9.9: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 17 Mar 2026, 14:07 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/siyuan-note/siyuan/kernelGo<=0.0.0-20260313024916-fd6526133bb3No fixed version yet
Identifiers
GHSA-fq2j-j8hc-8vw8 · CVE-2026-32938 · GO-2026-4722
Weakness (CWE)
CWE-22 · CWE-200 · CWE-284
Published
17 Mar 2026
Updated
30 Mar 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Vulnerable: the Go module github.com/siyuan-note/siyuan/kernel, all versions up to and including 0.0.0-20260313024916-fd6526133bb3. Per the source, an attacker with only a normal authenticated account on a publish service can make the desktop kernel copy local files referenced by file:// links in pasted HTML into the workspace assets directory, then read those copies through the assets endpoint. This can expose any sensitive file the process can read, such as credentials or configuration files. No fixed version is listed.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.9 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0047, the 41st percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:08 UTC First seen by agentprime
  2. 31 Oct 2026, 15:08 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.