{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-100633 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-100633 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-100633 is a high-severity path traversal vulnerability in siyuan-note siyuan, published on 26 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-100633 and fix it if it is affected.\n\nWhat it is: CVE-2026-100633 is a high-severity path traversal vulnerability in siyuan-note siyuan, published on 26 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-100633 in the wild and no public exploit code.\n\nAffected product: siyuan-note siyuan. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-100633/ (Markdown: https://insights.sbomify.com/CVE-2026-100633/index.md)","id":"CVE-2026-100633","markdown":"https://insights.sbomify.com/CVE-2026-100633/index.md","name":"CVE-2026-100633","record":{"aliases":["GHSA-9g6v-r3xf-673q","GHSA-x2gq-fcjj-cxqr"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"SiYuan knowledge management","requires_auth":"high_privilege","summary":"Authenticated administrators can bypass sensitive-path guards in MCP file operations to read or overwrite protected configuration and key files.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"SiYuan is a self-hosted personal knowledge management system. In versions 3.8.0 through 3.8.3, the MCP file tool's sensitive-path guard (util.IsForbiddenAbsPath(), invoked from resolvePath()) is applied only to the allowed root of recursive operations and not to each resolved descendant path — an incomplete fix for GHSA-c8r8-95hg-mp34. An authenticated administrator using the in-app Agent or the external MCP server can therefore bypass the protected-workspace-file denylist: file.grep can return matching lines from non-hidden protected descendants (for example conf/conf.json, TLS keys, data/snippets/conf.json, data/templates/, data/.siyuan/publishAccess.json, notebook .siyuan internals, or the kernel log), file.copy can copy protected descendants to an ordinary path where file.read can then retrieve them, and unzip can overwrite protected descendants using ordinary, lexically contained ZIP member names. Because file.grep is globally classified as a safe action, it receives no per-call confirmation, and the confirmation cards for file.copy and unzip show only the allowed root arguments. This issue is fixed in version 3.8.4. Suggested title: SiYuan 3.8.0 through 3.8.3 Sensitive-Path Guard Bypass in Recursive MCP File Operations.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-09-29","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-09-29T00:51:55Z","kind":"github_poc","ref":"https://github.com/dpfkdlemtp/CVE-2026-100633","stars":0,"title":"Published SiYuan CVE · Reporter: dpfkdlemtp · Official record and advisory links"}],"tier":"poc_unverified"},"has_fix":false,"headline":"SiYuan 3.8.0 through 3.8.3 Path Traversal via MCP File Operations","id":"CVE-2026-100633","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"SiYuan before v3.8.4 Missing Authorization via siyuan-send-windows","id":"CVE-2026-100634"},"packages":[],"prev":{"headline":"Parse Server 9.0.0 before 9.10.1 Protected Fields Disclosure via LiveQuery","id":"CVE-2026-100632"},"products":["siyuan"],"published":"2026-09-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-05","vendors":["siyuan-note"]},"summary":"Authenticated administrators can bypass sensitive-path guards in MCP file operations to read or overwrite protected configuration and key files.","url":"https://insights.sbomify.com/CVE-2026-100633/"}