Advisory record · GHSA-qvq9-hq6p-v378

SiYuan: Missing publish-access filter on getBlockAttrs and batchGetBlockAttrs discloses block attributes (name, alias, memo, custom fields) of protected documents

CVSS 6.9 MediumEPSS 0.0030 · 22nd percentile

Published by the GitHub Advisory Database at 3 Sept 2026, 22:58 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-20260724093256-229fdffd7e4a0.0.0-20260724093256-229fdffd7e4a
Identifiers
GHSA-qvq9-hq6p-v378 · CVE-2026-72803 · GO-2026-6404
Weakness (CWE)
CWE-862
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.

The SiYuan kernel package github.com/siyuan-note/siyuan/kernel is affected at versions before 0.0.0-20260724093256-229fdffd7e4a and is fixed in 0.0.0-20260724093256-229fdffd7e4a. The two attribute-lookup API endpoints, getBlockAttrs and batchGetBlockAttrs, do not check publish access, so an anonymous reader (when publish auth is disabled) or a publish reader account can retrieve block names, aliases, memos, tags and custom attributes from publish-forbidden or password-protected documents. Upgrade to the fixed version; no 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
6.9 Medium 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0030, the 22nd percentile, on 17 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.