# CVE-2026-45371: SiYuan: SiYuan publish-mode Reader can mutate Conf and SQL index via 8 ungated APIs

> Attackers with reader or editor roles can modify configuration and SQL index via ungated APIs in SiYuan publish mode.

- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 May 2026
- **Updated:** 15 May 2026
- **Also known as:** GHSA-gmmv-4cc5-wr9r, GO-2026-5402

## What is CVE-2026-45371?

CVE-2026-45371 is a high-severity missing authorization vulnerability in siyuan-note siyuan, published on 14 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SiYuan is an open-source personal knowledge management system. Prior to 3.7.0, SiYuan publish-mode Reader can mutate Conf and SQL index via 8 ungated APIs. POST /api/graph/getGraph, POST /api/graph/getLocalGraph, POST /api/sync/setSyncInterval, POST /api/storage/updateRecentDocViewTime, POST /api/storage/updateRecentDocCloseTime, POST /api/storage/updateRecentDocOpenTime, POST /api/storage/batchUpdateRecentDocCloseTime, and POST /api/search/updateEmbedBlock are registered with model.CheckAuth only, omitting both model.CheckAdminRole and model.CheckReadonly. Each of them writes server-side state, including atomic rewrites of <workspace>/conf/conf.json via model.Conf.Save(). Any caller whose JWT passes CheckAuth, including a publish-service RoleReader (the role assigned to anonymous publish visitors) and a RoleEditor against a workspace where Editor.ReadOnly = true, can hit them This vulnerability is fixed in 3.7.0.

Weakness: CWE-862 (Missing Authorization), CWE-285 (Improper Authorization)

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

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

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

Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260512140701-d7b77d945e0d or later.

## Is CVE-2026-45371 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45371 is a high-severity missing authorization vulnerability in siyuan-note siyuan, published on 14 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45371 exists.

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

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

## Sources

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

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