SiYuan: TLS Private Keys Readable via getFile (Incomplete Blocklist)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

• CVE-2026-85175: 0.33% estimated exploitation activity in the next 30 days; percentile 25.61 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary: IsForbiddenAbsPath() only blocks conf/conf.json by exact match. The TLS private key (conf/key.pem) and CA private key (conf/ca.key) live in the same conf/ directory and are absent from the blocklist. Any authenticated user can retrieve them via POST /api/file/getFile. Root cause kernel/util/pathguard.go, IsForbiddenAbsPath() has no entry for TLS key material. The getFile handler at kernel/api/file.go:497 skips the blocklist for RoleAdministrator, and in v3.8.1 all authenticated users receive RoleAdministrator (no non-admin role is currently issued to direct API consumers). The files are generated on every boot regardless of whether TLS is active. Steps to reproduce: Response: Raw PEM private key bytes. <img width="927" height="467" alt="2026-08-1914-19" src="https://github.com/user-attachments/assets/12e0787f-6bfc-416a-b5ad-a22954e45c48" / Impact: On deployments with TLS enabled (--ssl flag or NetworkServeTLS), possession of key.pem allows decryption of captured HTTPS…

Published by the source

5 Oct 2026, 17:32 UTC

Last modified by the source

7 Oct 2026, 17:55 UTC

Source last checked

26 Oct 2026, 15:29 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-4wwp-f6gw-6qm5

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6663

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-4wwp-f6gw-6qm5

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-85175

Advisory: SiYuan: TLS Private Keys Readable via getFile (Incomplete Blocklist)
IDs: CVE-2026-85175, GHSA-4wwp-f6gw-6qm5
Record: https://patchnext.com/advisories/cve-2026-85175 (revision 3, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/siyuan-note/siyuan/kernel 0.0.0-20260819144130-256d73aa7f94. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/siyuan-note/siyuan/kernel: affected < 0.0.0-20260819144130-256d73aa7f94; fixed in 0.0.0-20260819144130-256d73aa7f94

## Suggested inspection (read-only)
- Go github.com/siyuan-note/siyuan/kernel: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/siyuan-note/siyuan/kernel.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GO-2026-6663 (OSV record GO-2026-6663 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260819144130-256d73aa7f94 (fixed))
- Verified: https://osv.dev/vulnerability/GHSA-4wwp-f6gw-6qm5 (OSV record GHSA-4wwp-f6gw-6qm5 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260819144130-256d73aa7f94 (fixed))
- Verified: https://github.com/advisories/GHSA-4wwp-f6gw-6qm5 (GitHub-reviewed advisory GHSA-4wwp-f6gw-6qm5 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260819144130-256d73aa7f94)

Commands are suggestions: review each one before running it.