# CVE-2026-72796: SiYuan before v3.7.4 Access Control Bypass via Static Routes

> Attackers can bypass access controls to read sensitive templates and snippets by accessing static routes directly, bypassing REST API restrictions.

- **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-fgmr-7w36-9qfq, GO-2026-6423

## What is CVE-2026-72796?

CVE-2026-72796 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 before v3.7.4 contains an access control bypass vulnerability where static-file routes in the server mux bypass publish-access controls enforced on the REST API. Attackers with publish reader tokens or anonymous access in disabled-auth mode can read templates, snippets, and export artifacts by directly accessing static routes that lack the same restrictions as their REST API counterparts.

Weakness: CWE-862 (Missing Authorization)

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

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-20260725122641-34be6c0bb073 |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260725122641-34be6c0bb073 |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260725122641-34be6c0bb073 |

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

Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260725122641-34be6c0bb073 or later.

## Is CVE-2026-72796 being exploited?

There is no known exploitation of CVE-2026-72796 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72796 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: There is no known exploitation of CVE-2026-72796 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260725122641-34be6c0bb073
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260725122641-34be6c0bb073
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260725122641-34be6c0bb073

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-72796/ (Markdown: https://insights.sbomify.com/CVE-2026-72796/index.md)
```

## Sources

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

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