# SiYuan: Static-file routes bypass the publish-access controls enforced on the REST API, exposing templates, snippets and export artifacts to anonymous readers

Advisory record · `GHSA-fgmr-7w36-9qfq`

- **Identifiers:** `GHSA-fgmr-7w36-9qfq` · `CVE-2026-72796` · `GO-2026-6423`
- **State:** Confirmed
- **Severity:** CVSS 6.9 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-862](https://cwe.mitre.org/data/definitions/862.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 4 Sept 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 4 Sept 2026, 21:02 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/siyuan-note/siyuan/kernel` (Go): affected `<0.0.0-20260725122641-34be6c0bb073`; fixed in `0.0.0-20260725122641-34be6c0bb073`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Packages affected: the Go module github.com/siyuan-note/siyuan/kernel, versions before 0.0.0-20260725122641-34be6c0bb073, fixed in that version. Static-file routes in SiYuan's server, including /templates/, /snippets/, /widgets/, /plugins/, /emojis/ and /export/, skip the publish-access checks applied to the REST API. A publish reader, or an anonymous visitor when publish auth is disabled, can read template documents, snippet JS/CSS and export artifacts over the network. Upgrade to 0.0.0-20260725122641-34be6c0bb073 or later.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.9 Medium, CVSS 4.0: `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`, from CNA (VulnCheck)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0035, the 29th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:13 UTC: First seen by agentprime
- 31 Oct 2026, 14:13 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-fgmr-7w36-9qfq)

## Sources

- [GitHub Advisory Database: GHSA-fgmr-7w36-9qfq](https://github.com/advisories/GHSA-fgmr-7w36-9qfq)
- [OSV: GHSA-fgmr-7w36-9qfq](https://osv.dev/vulnerability/GHSA-fgmr-7w36-9qfq)
- <https://github.com/siyuan-note/siyuan/security/advisories/GHSA-fgmr-7w36-9qfq>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-72796>
- <https://github.com/siyuan-note/siyuan/commit/34be6c0bb0739d5b8e99ecc0cbfb474abb16230d>
- <https://github.com/siyuan-note/siyuan>
- <https://www.vulncheck.com/advisories/siyuan-before-access-control-bypass-via-static-routes>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-fgmr-7w36-9qfq>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-fgmr-7w36-9qfq/>. Everything for agents: <https://agentprime.io/llms.txt>.
