CVE-2026-72808: SiYuan Missing Publish-access Filter On GetFileAnnotation Vulnerability
MODERATECVE-2026-72808 is a MODERATE (CVSS 5.8) missing publish-access filter on getfileannotation vulnerability (CWE-862: Missing Authorization) affecting SiYuan libraries in the Go ecosystem. The issue involves missing publish-access filter on getfileannotation discloses private pdf annotations of forbidden/protected documents (publish mode). Remediation is available by upgrading affected packages to version 0.0.0-20260723031702-509b35055940.
CVE-2026-72808 at a Glance
Security Impact
CVSS: 5.8
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N).
How to Fix CVE-2026-72808
To remediate this vulnerability, upgrade all affected SiYuan dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260723031702-509b35055940
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/siyuan-note/siyuan/kernel
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-72808, inspect your project dependencies for SiYuan:
inspect dependencies for github.com/siyuan-note/siyuan/kernel
Analyze the terminal output to locate any version of SiYuan in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.0.0-20260723031702-509b35055940), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-862: Missing Authorization, where the product does not perform an authorization check when an actor attempts to access a resource or perform an action. In SiYuan, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-72808 Affected SiYuan Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/siyuan-note/siyuan/kernel
|
Go |
< 0.0.0-20260723031702-509b35055940
|
0.0.0-20260723031702-509b35055940
|
References
Frequently Asked Questions
What is CVE-2026-72808?
Which SiYuan versions are affected?
What version fixes CVE-2026-72808?
Is github.com/siyuan-note/siyuan/kernel affected?
What is the CVSS score of CVE-2026-72808?
What CWE is associated with CVE-2026-72808?
How can I check Go dependencies for CVE-2026-72808?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-v7ph-r5r6-4jcj",
"modified" : "2026-09-03T22:48:22Z",
"published" : "2026-09-03T22:48:22Z",
"aliases" : [ "CVE-2026-72808" ],
"summary" : "SiYuan: Missing publish-access filter on getFileAnnotation discloses private PDF annotations of forbidden/protected documents (publish mode)",
"details" : "**CVE:** This vulnerability corresponds to [CVE-2026-72808](https://nvd.nist.gov/vuln/detail/CVE-2026-72808).\n\n### Summary\n\nThe `/api/asset/getFileAnnotation` endpoint returns the content of `.sya` PDF-annotation files with no publish-access check. It is gated by `CheckAuth` only, so it is reachable by the publish `RoleReader` token and by the anonymous account when `Publish.Auth.Enable` is `false`. Its sibling, the `/assets/*` asset route does enforce publish access, including the publish password. An anonymous reader who knows an asset path can therefore read the private PDF annotations (highlights, notes) attached to assets in publish-forbidden, password-protected, or unpublished documents.\n\n### Details\n\n`getFileAnnotation` resolves the annotation file via `GetAssetAbsPathInBox` (no path traversal) and returns the `.sya` content. Unlike the `/assets/*` route, which applies the publish-access filter including password enforcement before serving asset bytes, `getFileAnnotation` applies no publish-access, publish-ignore, or password check. The guarded-sibling asymmetry indicates the boundary is meant to apply to this data and was omitted here.\n\n`.sya` files for encrypted-box assets are fail-closed and not exposed. The gap is limited to non-encrypted assets.\n\n**Route / auth tier.** `getFileAnnotation` is registered `CheckAuth`-only. `CheckAuth` admits `RoleReader`; the publish proxy forwards port-6808 traffic with a Reader JWT (anonymous when publish auth is disabled).\n\n### Proof of Concept\n\nReproduced on a local instance (publish mode on 6808, Basic Auth off).\n\n**Setup (admin, 6806):**\n1. `createNotebook{name:\"AnnotPoc\"}` → box\n2. `createDocWithMd{notebook, path:\"/annot-victim\", markdown:\"doc with a pdf\"}` → doc\n3. `POST /api/asset/upload` (multipart `id=<doc>`, `file[]=@secret.pdf`) → `assets/secret-...pdf`\n4. `setFileAnnotation{path:\"<asset>.sya\", data:\"{annotSecret:ANNOT_SECRET_4471,note:private highlight}\"}`\n5. `setPublishAccess{id:<doc>, visible:false, password:\"\", disable:true}` → doc forbidden\n\n**Exploit (anonymous reader, 6808, no token):**\n```\nPOST http://127.0.0.1:6808/api/asset/getFileAnnotation\n{\"path\":\"assets/secret-...pdf.sya\"}\n```\nReturns:\n```\n{\"code\":0,\"data\":{\"data\":\"{\\\"annotSecret\\\":\\\"ANNOT_SECRET_4471\\\",\\\"note\\\":\\\"private highlight\\\"}\"}}\n```\nThe annotation content of a publish-forbidden document is returned to an anonymous reader with no publish-access check, while the `/assets/*` route serving the same asset class enforces publish access and password.\n\n### Impact\n\nAn anonymous reader (publish mode with auth disabled) or any publish `RoleReader` can read the private PDF annotations (highlights and notes) of assets belonging to publish-forbidden, password-protected, or unpublished documents, given the asset path. This defeats the publish-access/password boundary for annotation data. Scope is limited to annotated PDFs in non-encrypted notebooks; encrypted-box annotations are not exposed. Confidentiality-only.\n\n### Suggested fix\n\nApply the same publish-access check the `/assets/*` route uses to `getFileAnnotation` resolve the asset's owning document and enforce the publish-access/publish-ignore / password check before returning `.sya` content.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/siyuan-note/siyuan/kernel"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.0.0-20260723031702-509b35055940"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/siyuan-note/siyuan/security/advisories/GHSA-v7ph-r5r6-4jcj"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-72808"
}, {
"type" : "WEB",
"url" : "https://github.com/siyuan-note/siyuan/commit/509b35055940856ec1c89cb4888723c4660b776a"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/siyuan-note/siyuan"
}, {
"type" : "WEB",
"url" : "https://www.vulncheck.com/advisories/siyuan-before-information-disclosure-via-getfileannotation"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-862" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-09-03T22:48:22Z",
"nvd_published_at" : null
}
}