# SiYuan vulnerable to Arbitrary file Read / SSRF in github.com/siyuan-note/siyuan/kernel

Advisory record · `GHSA-cv54-7wv7-qxcw`

- **Identifiers:** `GHSA-cv54-7wv7-qxcw` · `CVE-2026-23850` · `GO-2026-4347`
- **State:** Confirmed
- **Severity:** CVSS 7.8 High
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 3 Feb 2026
- **Updated:** 3 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 3 Feb 2026, 20:30 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-20260118092326-b2274baba2e1`; fixed in `0.0.0-20260118092326-b2274baba2e1`

## Machine-written summary

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

> SiYuan's kernel package (github.com/siyuan-note/siyuan/kernel) is affected in versions before 0.0.0-20260118092326-b2274baba2e1, and the fix is in that same version. The source gives few details beyond the title, which names arbitrary file read and server-side request forgery, so it does not say what access an attacker needs. Upgrade to 0.0.0-20260118092326-b2274baba2e1 or later.

Written 10 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

- 7.8 High, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`, from CNA (GitHub_M)

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

## Timeline

This record came from the full history of the GitHub Advisory Database, published 3 Feb 2026. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-cv54-7wv7-qxcw](https://github.com/advisories/GHSA-cv54-7wv7-qxcw)
- [OSV: GHSA-cv54-7wv7-qxcw](https://osv.dev/vulnerability/GHSA-cv54-7wv7-qxcw)
- <https://github.com/siyuan-note/siyuan/security/advisories/GHSA-cv54-7wv7-qxcw>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-23850>
- <https://github.com/siyuan-note/siyuan/blob/master/kernel/model/file.go#L1035>
- <https://github.com/siyuan-note/siyuan/blob/v3.4.2/kernel/api/filetree.go#L799-L886>
- <https://github.com/siyuan-note/siyuan/commit/b2274baba2e11c8cf8901b0c5c871e5b27f1f6dd>
- <https://github.com/siyuan-note/siyuan/commit/f8f4b517077b92c90c0d7b51ac11be1b34b273ad>
- <https://github.com/siyuan-note/siyuan/issues/16860>

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-cv54-7wv7-qxcw>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-cv54-7wv7-qxcw/>. Everything for agents: <https://agentprime.io/llms.txt>.
