# CVE-2026-85175: SiYuan before v3.8.2 TLS Private Key Disclosure via getFile

> Attackers can retrieve TLS private keys via an incomplete path blocklist, enabling traffic decryption and certificate forgery in SiYuan.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/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:** 3 Sep 2026
- **Updated:** 3 Sep 2026
- **Also known as:** GHSA-4wwp-f6gw-6qm5, GHSA-gg9w-4vv2-vjcm, GO-2026-6663

## What is CVE-2026-85175?

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

### Official description

SiYuan versions <= 3.8.1 (fixed in v3.8.2) contain an incomplete blocklist in the IsForbiddenAbsPath() function (kernel/util/path_guard.go), which only blocks conf/conf.json by exact match and does not restrict the TLS private key (conf/key.pem) or CA private key (conf/ca.key) stored in the same conf/ directory. Because the getFile handler skips the blocklist for RoleAdministrator and all authenticated users receive RoleAdministrator in v3.8.1, any user (or any client on a default no-auth-code instance) can retrieve these private keys via POST /api/file/getFile. On deployments with TLS enabled, this allows decryption of captured HTTPS traffic (key.pem) and forging of certificates trusted by clients that imported SiYuan's CA (ca.key).

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

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

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

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

Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260819144130-256d73aa7f94 or later.

## Is CVE-2026-85175 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85175 is a high-severity vulnerability in siyuan-note siyuan, published on 3 Sep 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-85175 exists.

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

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

## Sources

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

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