# CVE-2026-54066: SiYuan: Path Traversal via Double URL Encoding in /assets/*path (publish mode arbitrary file─read)

> Unauthenticated attackers can read arbitrary files, including sensitive credentials, via double URL encoding in publish mode.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Jun 2026
- **Updated:** 25 Jun 2026
- **Also known as:** GHSA-p4m3-mgmm-c664, GO-2026-5964

## What is CVE-2026-54066?

CVE-2026-54066 is a high-severity path traversal vulnerability in siyuan-note siyuan, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SiYuan is an open-source personal knowledge management system. Prior to 3.7.0, the patch for CVE-2026-41894 ("Path Traversal via Double URL Encoding") sanitized the /export/ route but the identical root cause remains in the /assets/*path route. In publish mode (anonymous read-only HTTP endpoint, default port 6808), an unauthenticated remote attacker can read arbitrary files inside WorkspaceDir — including conf/conf.json (which contains the AccessAuthCode SHA256 hash, API token, and sync keys), temp/siyuan.db, temp/blocktree.db, and siyuan.log — by double-URL-encoding .. segments. This vulnerability is fixed in 3.7.0.

Weakness: CWE-23 (Relative Path Traversal), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-1188 (Initialization of a Resource with an Insecure Default)

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

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

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

Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260628153353-2d5d72223df4 or later.

## Is CVE-2026-54066 being exploited?

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

Public exploit code:

- SiYuan <= 3.6.5 - Unauthenticated Path Traversal (nuclei): http/cves/2026/CVE-2026-54066.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54066 is a high-severity path traversal vulnerability in siyuan-note siyuan, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54066 exists.

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

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

## Sources

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

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