# CVE-2026-72808: SiYuan before v3.7.4 Information Disclosure via getFileAnnotation

> Attackers can read private PDF annotations from protected documents via an API endpoint lacking proper access checks.

- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-v7ph-r5r6-4jcj, GO-2026-6406

## What is CVE-2026-72808?

CVE-2026-72808 is a medium-severity missing authorization vulnerability in siyuan-note siyuan, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SiYuan 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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-72808?

3 open source packages ship an affected version, including github.com/siyuan-note/siyuan/kernel.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260723031702-509b35055940 |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260723031702-509b35055940 |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260723031702-509b35055940 |

## How do I fix CVE-2026-72808?

Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260723031702-509b35055940 or later.

## Is CVE-2026-72808 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72808 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72808 and fix it if it is affected.

What it is: CVE-2026-72808 is a medium-severity missing authorization vulnerability in siyuan-note siyuan, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72808 exists.

Affected packages and fixed versions:
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260723031702-509b35055940
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260723031702-509b35055940
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260723031702-509b35055940

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72808/ (Markdown: https://insights.sbomify.com/CVE-2026-72808/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72808
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72808
- OSV: https://osv.dev/vulnerability/CVE-2026-72808

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72808/
Summaries are generated and may contain mistakes; the official description above is the record.