# CVE-2026-33194: SiYuan has an Incomplete Fix for IsSensitivePath Denylist Allows File Read from /opt, /usr, /home

> An attacker can read sensitive files from system directories like /opt, /usr, and /home due to an incomplete path denylist in SiYuan.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Mar 2026
- **Updated:** 25 Mar 2026
- **Also known as:** GHSA-vm69-h85x-8p85, GO-2026-4766

## What is CVE-2026-33194?

CVE-2026-33194 is a medium-severity path traversal vulnerability in B3log Siyuan, published on 20 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

SiYuan is a personal knowledge management system. Prior to version 3.6.2, the `IsSensitivePath()` function in `kernel/util/path.go` uses a denylist approach that was recently expanded (GHSA-h5vh-m7fg-w5h6, commit 9914fd1) but remains incomplete. Multiple security-relevant Linux directories are not blocked, including `/opt` (application data), `/usr` (local configs/binaries), `/home` (other users), `/mnt` and `/media` (mounted volumes). The `globalCopyFiles` and `importStdMd` endpoints rely on `IsSensitivePath` as their primary defense against reading files outside the workspace. Version 3.6.2 contains an updated fix.

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

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

3 open source packages ship an affected version, including github.com/siyuan-note/siyuan/kernel. It affects 1 product.


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

Products: B3log Siyuan.

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

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

## Is CVE-2026-33194 being exploited?

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

## Other vulnerabilities in B3log Siyuan

- [CVE-2026-32938](https://insights.sbomify.com/CVE-2026-32938/): SiYuan has an Arbitrary File Read in its Desktop Publish Service (critical 9.9)
- [CVE-2026-33669](https://insights.sbomify.com/CVE-2026-33669/): SiYuan has Arbitrary Document Reading within the Publishing Service (critical 9.8)
- [CVE-2026-33670](https://insights.sbomify.com/CVE-2026-33670/): SiYuan has directory traversal within its publishing service (critical 9.8)
- [CVE-2026-32767](https://insights.sbomify.com/CVE-2026-32767/): SiYuan: Authorization Bypass Allows Arbitrary SQL Execution via Search API (critical 9.8)
- [CVE-2024-53504](https://insights.sbomify.com/CVE-2024-53504/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33194 is a medium-severity path traversal vulnerability in B3log Siyuan, published on 20 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33194 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.2
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 3.6.2

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

## Sources

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

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