Path Traversal in github.com/siyuan-note/siyuan/kernel (CVE-2026-69086)
Summary
Path traversal in github.com/siyuan-note/siyuan/kernel (CVE-2026-69086). Confidential information can be exposed externally. Exploitable via POST /api/av/renderAttributeView. Mitigation: upgrade to 0.0.0-20260720151813-0f5a0e7c67b0 or later.
Original description
The description as published by the source.
CVE: This vulnerability corresponds to CVE-2026-69086.
Summary
Four attribute-view read endpoints build a filesystem path from a caller-controlled id/avID and read it without confining the result to the attribute-view storage directory (DataDir/storage/av/). On the load (file-exists) code path there is no boundary check, so an avID containing ../ segments escapes storage/av/ and causes the kernel to read a .json file elsewhere in the workspace.
The endpoints require only CheckAuth, which the publish service's RoleReader token satisfies; when Publish.Auth.Enable is false the publish proxy uses the anonymous account, making the surface reachable with no credentials.
Details
Affected endpoints (all gated by CheckAuth only, no CheckAdminRole):
POST /api/av/renderAttributeView→arg["id"]POST /api/av/getAttributeViewKeysByID→arg["avID"]POST /api/av/getAttributeViewKeys→arg["id"]POST /api/av/getCurrentAttrViewImages→arg["id"]
In model.RenderAttributeView (model/attribute_view_render.go), the only identifier guard ast.IsNodeIDPattern(avID) sits inside the if !filelock.IsExist(existPath) (create) branch:
existPath = GetAttributeViewDataPath(avID) // path built from avID, no check
if !filelock.IsExist(existPath) { // NOT-EXIST / CREATE branch
if !createIfNotExist {
return // NotFound
}
if…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-69086 has been found in github.com/siyuan-note/siyuan/kernel.
Attackers can target a specific entry point like POST /api/av/renderAttributeView over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.7/10.
What to do: upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260720151813-0f5a0e7c67b0 or later.
If unsure, ask your IT team or search "github.com/siyuan-note/siyuan/kernel CVE-2026-69086" on the vendor's site.
CVE-2026-69086 (github.com/siyuan-note/siyuan/kernel) — CWE-22 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/av/renderAttributeView / POST /api/av/getAttributeViewKeysByID / POST /api/av/getAttributeViewKeys / POST /api/av/getCurrentAttrViewImages
Patched: 0.0.0-20260720151813-0f5a0e7c67b0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in github.com/siyuan-note/siyuan/kernel. Attackers reach the vulnerable code path via POST /api/av/renderAttributeView.
Check the vendor advisory for the affected versions of github.com/siyuan-note/siyuan/kernel. Attack surface: POST /api/av/renderAttributeView / POST /api/av/getAttributeViewKeysByID / POST /api/av/getAttributeViewKeys / POST /api/av/getCurrentAttrViewImages.
Severity: High (CVSS 7.7/10). Confidential information can be exposed externally.
Update to 0.0.0-20260720151813-0f5a0e7c67b0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /api/av/renderAttributeView requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/siyuan-note/siyuan/kernel' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/siyuan-note/siyuan/kernel' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/siyuan-note/siyuan/kernelを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /api/av/renderAttributeView' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/av/renderAttributeViewへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260720151813-0f5a0e7c67b0ステージング環境で 0.0.0-20260720151813-0f5a0e7c67b0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/av/renderAttributeView on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web nvd.nist.gov
- web vulncheck.com
- web github.com
- web github.com