# CVE-2026-69086: SiYuan before v3.7.3 Path Traversal via unvalidated avID > Attackers can read JSON files outside the intended directory via path traversal in SiYuan, disclosing sensitive database content. - **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 3 Aug 2026 - **Updated:** 14 Aug 2026 - **Also known as:** GHSA-7hm9-v7vf-7g4w, GO-2026-6373 ## What is CVE-2026-69086? CVE-2026-69086 is a high-severity path traversal vulnerability in siyuan-note siyuan, published on 3 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description SiYuan versions before v3.7.3 fail to validate the avID parameter on all code branches in attribute-view read endpoints, allowing attackers to construct traversal paths that escape the storage directory. Authenticated users with RoleReader permissions or anonymous clients when publish authentication is disabled can read JSON files outside the attribute-view directory to disclose cross-scope database content. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2026-69086? 3 open source packages ship an affected version, including github.com/siyuan-note/siyuan/kernel. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260720151813-0f5a0e7c67b0 | | `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260720151813-0f5a0e7c67b0 | | `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260720151813-0f5a0e7c67b0 | ## How do I fix CVE-2026-69086? Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260720151813-0f5a0e7c67b0 or later. ## Is CVE-2026-69086 being exploited? There is no known exploitation of CVE-2026-69086 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-69086 and fix it if it is affected. What it is: CVE-2026-69086 is a high-severity path traversal vulnerability in siyuan-note siyuan, published on 3 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-69086 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260720151813-0f5a0e7c67b0 - github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260720151813-0f5a0e7c67b0 - github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260720151813-0f5a0e7c67b0 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-69086/ (Markdown: https://insights.sbomify.com/CVE-2026-69086/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-69086 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-69086 - OSV: https://osv.dev/vulnerability/CVE-2026-69086 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-69086/ Summaries are generated and may contain mistakes; the official description above is the record.