# CVE-2026-41894: SiYuan: Incomplete Fix Bypass for CVE-2026-30869: Path Traversal via Double URL Encoding in `/export/` Endpoint

> An authenticated attacker can bypass path traversal protections via double URL encoding to read arbitrary workspace files, including the database and user documents.

- **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:** Yes
- **Published:** 24 Apr 2026
- **Updated:** 27 Apr 2026
- **Also known as:** GHSA-hjh7-r5w8-5872, GO-2026-5429

## What is CVE-2026-41894?

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

### Official description

SiYuan is an open-source personal knowledge management system. Prior to 3.6.5, the fix for CVE-2026-30869 only added a denylist check (IsSensitivePath) but did not address the root cause — a redundant url.PathUnescape() call in serveExport(). An authenticated attacker can use double URL encoding (%252e%252e) to traverse directories and read arbitrary workspace files including the full SQLite database (siyuan.db), kernel log, and all user documents. This vulnerability is fixed in 3.6.5.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

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 | None |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 3.6.5 |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 3.6.5 |

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

Upgrade github.com/siyuan-note/siyuan/kernel to 3.6.5 or later.

## Is CVE-2026-41894 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41894 is a high-severity path traversal vulnerability in siyuan-note siyuan, published on 24 Apr 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-41894 exists.

Affected packages and fixed versions:
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; no fix listed
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 3.6.5
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 3.6.5

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

## Sources

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

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