Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-72800 medium CVSS 5.8

Vulnerability in github.com/siyuan-note/siyuan/kernel (CVE-2026-72800)

Summary

Vulnerability in github.com/siyuan-note/siyuan/kernel (CVE-2026-72800). Risk of unauthorized operations or information disclosure. Exploitable via POST /api/av/getAttributeViewKeysByID. Mitigation: upgrade to 0.0.0-20260724103335-f36331956ae9 or later.

Original description

The description as published by the source.

CVE: This vulnerability corresponds to CVE-2026-72800.

Summary

POST /api/av/getAttributeViewKeysByID returns a database's full column schema with no publish-access filtering, while its sibling getAttributeViewKeys applies the filter for reader sessions. Two further endpoints, getBlockDefIDsByRefText and getBlockRelevantIDs return workspace-wide block IDs with no publish scoping. All three are CheckAuth-only, so they are reachable by the publish RoleReader token and by the anonymous account when Publish.Auth.Enable is false.

Details

(a) getAttributeViewKeysByID: ungated column-schema disclosure

The entire handler (kernel/api/av.go, router line 548):

ret.Data = model.GetAttributeViewKeysByID(avID, keyIDs...)   // no publish gate

With an empty keyIDs, GetAttributeViewKeysByID calls av.ParseAttributeView(avID) and returns every column's *av.Key:

Field Discloses
Name, Desc column title and user-authored description
Options the full single/multi-select vocabulary and colours (e.g. status labels such as "Fired", "Confidential")
Template the column's Sprig template expression — logic and field references
Relation the target avID, allowing pivot to another database
Rollup, NumberFormat, date config further schema

Guarded-sibling asymmetry, same file: getAttributeViewKeys (router line 526) runs `FilterBlockA…

Source: NIST National Vulnerability Database 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-72800 has been found in github.com/siyuan-note/siyuan/kernel.
Attackers can target a specific entry point like POST /api/av/getAttributeViewKeysByID over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.8/10.
What to do: upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260724103335-f36331956ae9 or later.
If unsure, ask your IT team or search "github.com/siyuan-note/siyuan/kernel CVE-2026-72800" on the vendor's site.

CVE-2026-72800 (github.com/siyuan-note/siyuan/kernel) — CWE-862 / CVSS v3 5.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /api/av/getAttributeViewKeysByID / getAttributeViewKeys / getBlockDefIDsByRefText / getBlockRelevantIDs
Patched: 0.0.0-20260724103335-f36331956ae9 — 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.

❓ What is the problem

A vulnerability (CWE-862) exists in github.com/siyuan-note/siyuan/kernel. Attackers reach the vulnerable code path via POST /api/av/getAttributeViewKeysByID without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/siyuan-note/siyuan/kernel. Attack surface: POST /api/av/getAttributeViewKeysByID / getAttributeViewKeys / getBlockDefIDsByRefText / getBlockRelevantIDs.

🔥 Severity

Severity: Medium (CVSS 5.8/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.0.0-20260724103335-f36331956ae9.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual POST /api/av/getAttributeViewKeysByID 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

  1. 1
    Identify 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 し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'POST /api/av/getAttributeViewKeysByID' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /api/av/getAttributeViewKeysByID への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260724103335-f36331956ae9

    ステージング環境で 0.0.0-20260724103335-f36331956ae9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against POST /api/av/getAttributeViewKeysByID on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

go github.com/siyuan-note/siyuan/kernel
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.0-20260724103335-f36331956ae9"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details