# CVE-2026-85578: SiYuan through 3.8.1 Authorization Bypass via getFile

> Attackers with reader role can access private workspace files in SiYuan by bypassing authorization checks on the getFile API endpoint.

- **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:** 8 Oct 2026
- **Also known as:** GHSA-8ggq-wq3f-vxrw, GHSA-fv97-ww8v-fw2w

## What is CVE-2026-85578?

CVE-2026-85578 is a high-severity missing authorization 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 through 3.8.1 contains an authorization bypass vulnerability in the /api/file/getFile endpoint that allows readers to retrieve files from notebooks explicitly configured as Visible:false. Attackers with reader role can access private workspace files including notebook metadata and internal configuration by knowing the hidden notebook identifier and file path.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-85578 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85578 is a high-severity missing authorization 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-85578 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-85578/ (Markdown: https://insights.sbomify.com/CVE-2026-85578/index.md)
```

## Sources

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

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