# CVE-2026-85583: SiYuan before v3.8.2 Path Traversal via symlink in file API

> Attackers with reader role can read arbitrary files outside the workspace by exploiting symlink handling in the file API.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-g7gf-v79m-jwrm, GHSA-g886-mc2m-v27v

## What is CVE-2026-85583?

CVE-2026-85583 is a high-severity path traversal vulnerability in siyuan-note siyuan, published on 4 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SiYuan versions before v3.8.2 contain a path traversal vulnerability in the reader-accessible file-read endpoint that follows symlinks when opening authorized asset paths. Attackers with reader role can request a logical asset under data/assets/ that is a symlink to a file outside the workspace and receive the target file bytes, bypassing workspace boundary restrictions.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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


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

No fix has been published for CVE-2026-85583 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-85583 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85583 is a high-severity path traversal vulnerability in siyuan-note siyuan, published on 4 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-85583 in the wild and no public exploit code.

Affected product: siyuan-note siyuan. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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