The CVE describes an authorization bypass in SiYuan's annotation endpoint, but the deeper issue is architectural: the codebase conflates authentication with authorization, treating 'am I logged in' as equivalent to 'does this document allow access.' This pattern has recurred across Django, Rails, Express, and Spring—not because developers are careless, but because authentication checks are built into frameworks while authorization logic requires understanding domain-specific access policies. SiYuan's publish system defines three distinct access categories (publish-forbidden, password-protected, unpublished), and the /assets/* route correctly enforces all three. But /api/asset/getFileAnnotation only checks authentication, allowing any authenticated user to read annotations on documents they shouldn't access. The v3.7.4 patch likely hardens this endpoint, but the real question is whether other endpoints carry the same gap. CheckAuth-as-authorization-proxy is a documented anti-pattern precisely because it scales poorly—each new endpoint inherits the cognitive shortcut, creating a distributed authorization gap invisible until specific paths are audited. Prioritization matters more than the CVSS 5.8 suggests: annotations contain the intellectual work itself, often more sensitive than the documents they annotate. If asset paths are enumerable across notebooks, this becomes bulk intellectual property exfiltration against users who disabled publish authentication—trusting SiYuan's architecture to protect what the UI explicitly allows. Audit your SiYuan deployment for other CheckAuth-only endpoints, and treat this CVE as evidence of a class of vulnerability rather than an isolated fix.
CVE-2026-72808
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSiYuan versions up to and including v3.7.2 (fixed in v3.7.4) contain an information disclosure vulnerability in the /api/asset/getFileAnnotation endpoint, which returns .sya PDF-annotation file content without a publish-access check. Because the endpoint is gated only by CheckAuth (unlike the /assets/* route, which enforces publish access and password), an anonymous reader (when publish authentication is disabled) or any publish RoleReader who knows an asset path can read the private PDF annotations (highlights and notes) of publish-forbidden, password-protected, or unpublished documents. The issue is limited to non-encrypted notebooks; encrypted-box annotations are not exposed.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysisThe application checks who you are but not whether you're allowed to perform a given action, so any authenticated user can reach things meant for others. This is the classic “change the ID in the URL” bug. The fix is an authorization check on every request, evaluated against the acting user's permissions.
General guidance for the missing authorization class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedv3.7.4
- Backup your SiYuan data before upgrading (locate the data folder and create a copy)
- Stop the running SiYuan application
- Download SiYuan v3.7.4 from the official GitHub releases page (github.com/siyuan-note/siyuan/releases)
- Install the v3.7.4 update over your existing installation
- Restart SiYuan and verify the application runs normally
- Test that the /api/asset/getFileAnnotation endpoint now properly enforces publish-access checks
- Confirm your private PDF annotations on non-encrypted notebooks are no longer accessible without proper authorization
Generated from the published advisory — verify against the referenced sources before acting.
There is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.
Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.
We develop and verify an original fix where the vendor hasn’t, from $4,000. Deployed to your staging first — never straight to production.
Scope it with usSee what else the community needs solved on the solutions-needed board.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-72808 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesThe CVE describes an authorization bypass in SiYuan's annotation endpoint, but the deeper issue is architectural: the codebase conflates authentication with authorization, treating 'am I logged in' as equivalent to 'does this document allow access.' This pattern has recurred across Django, Rails, Express, and Spring—not because developers are careless, but because authentication checks are built into frameworks while authorization logic requires understanding domain-specific access policies. SiYuan's publish system defines three distinct access categories (publish-forbidden, password-protected, unpublished), and the /assets/* route correctly enforces all three. But /api/asset/getFileAnnotation only checks authentication, allowing any authenticated user to read annotations on documents they shouldn't access. The v3.7.4 patch likely hardens this endpoint, but the real question is whether other endpoints carry the same gap. CheckAuth-as-authorization-proxy is a documented anti-pattern precisely because it scales poorly—each new endpoint inherits the cognitive shortcut, creating a distributed authorization gap invisible until specific paths are audited. Prioritization matters more than the CVSS 5.8 suggests: annotations contain the intellectual work itself, often more sensitive than the documents they annotate. If asset paths are enumerable across notebooks, this becomes bulk intellectual property exfiltration against users who disabled publish authentication—trusting SiYuan's architecture to protect what the UI explicitly allows. Audit your SiYuan deployment for other CheckAuth-only endpoints, and treat this CVE as evidence of a class of vulnerability rather than an isolated fix.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-72808 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data