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

Authorization Flaw in github.com/siyuan-note/siyuan/kernel (CVE-2026-72792)

Summary

Vulnerability in github.com/siyuan-note/siyuan/kernel (CVE-2026-72792). Risk of unauthorized operations or information disclosure. Exploitable via POST /api/tag/getTag. Mitigation: upgrade to 0.0.0-20260726002639-4515fa257cfa or later.

Original description

The description as published by the source.

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

Summary

/api/tag/getTag filters its results for reader roles through FilterTagsByPublishIgnore, which checks only the visible publish tier. Documents that are published but password-protected pass that check, so a reader who has never entered a document's publish password receives every tag label used inside it, together with occurrence counts.

The project has already treated this exact tier mismatch as a vulnerability on a sibling path: commit 82e9ded42 ("Enforce publish access for graph nodes") moved the graph endpoint off the visible-only filter and onto a password-aware one. FilterTagsByPublishIgnore was not upgraded alongside it.

Details

Item Detail
Route kernel/api/router.go:194 POST /api/tag/getTag → model.CheckAuth → getTag
Middleware CheckAuth only: no CheckReadonly, no CheckAdminRole
Guard Present but at the wrong tier: visible-only, no password check
Exposed Every tag label (#label# text) and its occurrence count inside password-protected but visible documents

The tier mismatch. For reader roles, getTag filters via:

publishIgnore := GetInvisiblePublishAccess(publishAccess)
tags = FilterTagsByPublishIgnore(publishIgnore, tags)

FilterTagsByPublishIgnore counts a label if CheckPathAccessableByPublishIgnore(span.Box, span.Path, publishIgnore) holds, then reads…

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-72792 has been found in github.com/siyuan-note/siyuan/kernel.
Attackers can target a specific entry point like POST /api/tag/getTag 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-20260726002639-4515fa257cfa or later.
If unsure, ask your IT team or search "github.com/siyuan-note/siyuan/kernel CVE-2026-72792" on the vendor's site.

CVE-2026-72792 (github.com/siyuan-note/siyuan/kernel) — CWE-863 / CVSS v3 5.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /api/tag/getTag / FilterTagsByPublishIgnore / model.CheckAuth / getTag
Patched: 0.0.0-20260726002639-4515fa257cfa — 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

Incorrect authorization (CWE-863) exists in github.com/siyuan-note/siyuan/kernel. Attackers reach the vulnerable code path via POST /api/tag/getTag without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/siyuan-note/siyuan/kernel. Attack surface: POST /api/tag/getTag / FilterTagsByPublishIgnore / model.CheckAuth / getTag.

🔥 Severity

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

🔧 How to fix

Update to 0.0.0-20260726002639-4515fa257cfa.

🛡️ 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/tag/getTag 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/tag/getTag' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

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

  3. 3
    Apply patch patch 
    Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260726002639-4515fa257cfa

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

  4. 4
    Post-deployment verification verify 
    Replay attack against POST /api/tag/getTag 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-20260726002639-4515fa257cfa"}]}]

References

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