Advisory record · GHSA-99rq-75j6-5j9f

SiYuan: Stored and reflected XSS in SiYuan through an SVG sanitizer bypass

CVSS 9.3 CriticalCriticalEPSS 0.0034 · 27th percentile

Critical, because:

  • CVSS score 9.3: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 3 Sept 2026, 14:53 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-20260714095344-f08dee71ba8e0.0.0-20260714095344-f08dee71ba8e
Identifiers
GHSA-99rq-75j6-5j9f · CVE-2026-66394 · GO-2026-6364
Weakness (CWE)
CWE-79
Published
3 Sept 2026
Updated
10 Sept 2026

Machine-written summary

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

SiYuan (Go kernel github.com/siyuan-note/siyuan/kernel) has a stored and reflected cross-site scripting flaw in its SVG sanitizer, where a script hidden in an SVG survives cleaning and runs when the file is opened directly. A signed-in user can be targeted by a single link to the dynamic icon endpoint, or by a planted SVG asset, and the script can then call the kernel API. The affected and fixed version fields both list 0.0.0-20260714095344-f08dee71ba8e, so upgrade to that version or later. No separate workaround is given.

Written 1 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.3 Critical 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0034, the 27th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:13 UTC First seen by agentprime
  2. 31 Oct 2026, 14:13 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.