# CVE-2026-82233: SiYuan before v3.8.1 Path Traversal via asset.upload

> Attackers can exploit prompt injection to upload sensitive files outside the workspace via the asset.upload tool, exposing credentials.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:N/VA:N/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 28 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-m4pm-qxhv-84p5, GHSA-p23f-cm6q-2qp8, GO-2026-6655

## What is CVE-2026-82233?

CVE-2026-82233 is a medium-severity path traversal vulnerability in siyuan-note siyuan, published on 28 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

SiYuan before v3.8.1 contains a path traversal vulnerability in the asset.upload MCP tool that accepts arbitrary absolute file paths without workspace boundary validation. Attackers can induce the AI Agent to upload sensitive files such as SSH keys or credentials from outside the workspace into the asset directory through prompt injection.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

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

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

Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260813142104-b26a4a307b8a or later.

## Is CVE-2026-82233 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82233 is a medium-severity path traversal vulnerability in siyuan-note siyuan, published on 28 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82233 exists.

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

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

## Sources

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

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