SiYuan: authFilePublishAccess distinguishes hidden and forbidden documents from public and nonexistent ones, and issues a publish-auth cookie for documents it reports as forbidden

Why it is Yellow

• CVSS 5.8 medium
• Public exploit or proof of concept referenced
• On your watchlist: Go

Affected packages

References

• https://github.com/advisories/GHSA-4pjg-x8qj-33j5
• https://github.com/siyuan-note/siyuan/security/advisories/GHSA-4pjg-x8qj-33j5
• https://nvd.nist.gov/vuln/detail/CVE-2026-73630
• https://github.com/siyuan-note/siyuan/commit/c7522b8db586ef1e1d6fa98bbe7ca0eb9d019efe
• https://github.com/siyuan-note/siyuan/releases/tag/v3.7.4-alpha.4
• https://www.vulncheck.com/advisories/siyuan-before-information-disclosure-via-authfilepublishaccess
• https://github.com/advisories/GHSA-4pjg-x8qj-33j5

Original description

SiYuan before v3.7.4 contains an information disclosure vulnerability in the /api/filetree/authFilePublishAccess endpoint, which is registered with CheckAuth only and is reachable anonymously. The endpoint never sets a failure code, so its outcome is signalled entirely by the response message and by the presence of a Set-Cookie header, and these signals differ across access tiers. By submitting requests with an empty password for a candidate document identifier, an anonymous attacker can distinguish whether a document is public/nonexistent, password-protected, or exists at the hidden or forbidden tier, thereby confirming the existence of documents they are not permitted to access. Because hidden and forbidden entries store an empty password, such requests also cause the server to issue a publish-auth cookie for forbidden documents.