CVE-2026-33669 SiYuan has Arbitrary Document Reading within the Publishing Service
Critical 9.8
Published
Updated
Check this codebase for CVE-2026-33669 and fix it if it is affected.
What it is: CVE-2026-33669 is a critical vulnerability in B3log Siyuan, published on 26 Mar 2026.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33669 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; no fix listed
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; no fix listed
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions up to 0.0.0-20260317012524-fe4523fff2c8; no fix listed
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions up to 0.0.0-20260317012524-fe4523fff2c8; no fix listed
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-33669/ (Markdown: https://insights.sbomify.com/CVE-2026-33669/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2026-33669?
CVE-2026-33669 is a critical vulnerability in B3log Siyuan, published on 26 Mar 2026.
Official description
SiYuan is a personal knowledge management system. Prior to version 3.6.2, document IDs were retrieved via the /api/file/readDir interface, and then the /api/block/getChildBlocks interface was used to view the content of all documents. Version 3.6.2 patches the issue.
Weakness: CWE-125
Which versions are affected by CVE-2026-33669?
5 open source packages ship an affected version, including github.com/siyuan-note/siyuan/kernel. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/siyuan-note/siyuan/kernel Go | All versions | None |
github.com/siyuan-note/siyuan/kernel Go | All versions | None |
github.com/siyuan-note/siyuan/kernel Go | All versions | None |
github.com/siyuan-note/siyuan/kernel Go | All versions to 0.0.0-20260317012524-fe4523fff2c8 | None |
github.com/siyuan-note/siyuan/kernel Go | All versions to 0.0.0-20260317012524-fe4523fff2c8 | None |
Products include B3log Siyuan.
How do I fix CVE-2026-33669?
Upgrade to a fixed version.
Is CVE-2026-33669 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33669 exists.
Other vulnerabilities in B3log Siyuan
- CVE-2026-32938 SiYuan has an Arbitrary File Read in its Desktop Publish Service
- CVE-2026-33670 SiYuan has directory traversal within its publishing service
- CVE-2026-32767 SiYuan: Authorization Bypass Allows Arbitrary SQL Execution via Search API
- CVE-2024-53504 SQL injection in n/a
- CVE-2024-53505 SQL injection in n/a
Sources
Also known as GHSA-34xj-66v3-6j83, GO-2026-4842.