Skip to content
SiYuan publish-mode flaws expose protected document assets to anonymous requests

SiYuan publish-mode flaws expose protected document assets to anonymous requests

First seen 22 Nov 2026, 12:13 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 22, 2026 at 12:14 UTC
  • •Two SiYuan advisories describe anonymous access to protected document assets when publish mode is enabled.
  • •The first flaw leaks asset paths and indexed text tied to publish-disabled attribute-view rows, tested at revision bfe3610.
  • •The second flaw serves a password-protected document's asset when a visible document shares the same relative asset name.
  • •The second advisory says Basic Auth deployments require a valid Reader account, which limits exposure there.
  • •The articles report reproductions in test harnesses and do not report exploitation in the wild or list fixed versions.

Two GitHub security advisories published 2026-11-22 for the SiYuan note-taking application describe access-control flaws in its public publish feature. The first (GHSA-q2x4-crw5-q567) reports that an anonymous request to the production publish listener can obtain the path and full indexed text of an asset referenced only by a publish-disabled attribute-view row, via /api/asset/getDocAssets and /api/getAssetContentByPath, tested at revision bfe3610. The second (GHSA-xxqp-6jxw-qr84) reports that GET /assets/ can serve a password-protected document's asset when a different visible document references the same relative name and the resolver selects the protected file. In that route test the protected canary was returned with HTTP 200, while a protected-only name returned HTTP 403. The second advisory states this applies to public publishing with Basic Auth disabled; Basic Auth deployments require a valid Reader account. Both advisories are published by the project itself and describe probe or route-test reproductions rather than observed exploitation. Neither article in the cluster provides CVE identifiers, CVSS scores, patch versions, or exploitation reports.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Timeline

2026-11-22
SiYuan advisory GHSA-q2x4-crw5-q567 published
Advisory describes anonymous leakage of publish-disabled attribute-view asset text via the public publish listener, tested at revision bfe3610.
github.com
2026-11-22
SiYuan advisory GHSA-xxqp-6jxw-qr84 published
Advisory reports GET /assets/ returned a protected document's asset with HTTP 200 in a route test, while a protected-only name returned HTTP 403.
github.com

More articles in this cluster (2)

Following this threat?

Track SiYuan in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

Am I affected if I use SiYuan publishing?
The advisories say the flaws apply to public publishing; the second states it applies when Basic Auth is disabled, and Basic Auth deployments require a valid Reader account. The articles do not list affected version ranges beyond the tested revision bfe3610.
Is this being exploited?
The articles do not report exploitation in the wild. They describe probe and route-test reproductions in the advisories themselves.
What should we do first?
The articles do not name a fixed version or patch. Restrict or disable public publish mode and review which documents and attribute views are published until an update is confirmed.