{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-82650 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-82650 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-82650 is a medium-severity path traversal vulnerability in siyuan-note siyuan, published on 30 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-82650 and fix it if it is affected.\n\nWhat it is: CVE-2026-82650 is a medium-severity path traversal vulnerability in siyuan-note siyuan, published on 30 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-82650 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-82650/ (Markdown: https://insights.sbomify.com/CVE-2026-82650/index.md)","id":"CVE-2026-82650","markdown":"https://insights.sbomify.com/CVE-2026-82650/index.md","name":"CVE-2026-82650","record":{"aliases":["GHSA-9jfx-rc58-h23j","GHSA-j5w2-98qv-mp97"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SiYuan note-taking app","requires_auth":"high_privilege","summary":"An authenticated attacker can read sensitive workspace files, including API tokens, via a path traversal vulnerability in the template rendering endpoint.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-668","name":"Exposure of Resource to Wrong Sphere"}],"description":"SiYuan 3.8.0 contains a path traversal / sensitive file exposure vulnerability in the RenderTemplate function (kernel/model/template.go), reachable via the POST /api/template/render endpoint (kernel/api/template.go). The endpoint restricts the supplied path only to the workspace directory (util.IsAbsPathInWorkspace) but, unlike the file API's refuseToAccess() blocklist, applies no sensitive-path exclusion. This allows an authenticated attacker to read sensitive workspace files, including conf/conf.json, which contains the API token and cookie signing key. The issue is fixed in v3.8.1.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"SiYuan before v3.8.1 Path Traversal via /api/template/render","id":"CVE-2026-82650","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.1 Missing Authorization via /history and /repo/diff","id":"CVE-2026-82651"},"packages":[],"prev":{"headline":"SiYuan before 3.8.1 Local Privilege Escalation via Uncontrolled Search Path","id":"CVE-2026-82649"},"products":["siyuan"],"published":"2026-08-30","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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-31","vendors":["siyuan-note"]},"summary":"An authenticated attacker can read sensitive workspace files, including API tokens, via a path traversal vulnerability in the template rendering endpoint.","url":"https://insights.sbomify.com/CVE-2026-82650/"}