Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-56397 critical CVSS 9.6

Cross-Site Scripting (XSS) in github.com/siyuan-note/siyuan/kernel (CVE-2026-56397)

Summary

Cross-site scripting in github.com/siyuan-note/siyuan/kernel (CVE-2026-56397). Successful exploitation can lead to full system takeover. Exploitable via displayName.

Original description

The description as published by the source.

Remote Code Execution via Malicious Bazaar Package — Marketplace XSS

Summary

SiYuan's Bazaar (community marketplace) renders plugin/theme/template metadata and README content without sanitization. A malicious package author can achieve RCE on any user who browses the Bazaar by:

  1. Package metadata XSS (zero-click): Package displayName and description fields are injected directly into HTML via template literals without escaping. Just loading the Bazaar page triggers execution.
  2. README XSS (one-click): The renderREADME function uses lute.New() without SetSanitize(true), so raw HTML in the README passes through to innerHTML unsanitized.

Both vectors execute in Electron's renderer with nodeIntegration: true and contextIsolation: false, giving full OS command execution.

Affected Component

  • Metadata rendering: app/src/config/bazaar.ts:275-277
  • README rendering (backend): kernel/bazaar/package.go:635-645 (renderREADME)
  • README rendering (frontend): app/src/config/bazaar.ts:607 (innerHTML)
  • Electron config: app/electron/main.js:422-426 (nodeIntegration: true)
  • Version: SiYuan <= 3.5.9

Vulnerable Code

Vector 1: Package metadata — no HTML escaping (bazaar.ts:275-277)

// Package name injected directly into HTML template — NO escaping
${item.preferredName}${item.preferredName !== item.name
    ? ` ${item.name}` : ""}

// Package description injected directly — NO escaping

    ${item.pr…

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-56397 has been found in github.com/siyuan-note/siyuan/kernel.
Attackers can target a specific entry point like displayName over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.6/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "github.com/siyuan-note/siyuan/kernel CVE-2026-56397" on the vendor's site.

CVE-2026-56397 (github.com/siyuan-note/siyuan/kernel) — CWE-79 / CVSS v3 9.6
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: displayName / description / renderREADME / innerHTML
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

Cross-site scripting (XSS) (CWE-79) exists in github.com/siyuan-note/siyuan/kernel. Attackers reach the vulnerable code path via displayName without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/siyuan-note/siyuan/kernel. Attack surface: displayName / description / renderREADME / innerHTML.

🔥 Severity

Severity: Critical (CVSS 9.6/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ 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 request patterns matching this CVE's known IOCs. 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
    Post-deployment verification verify 
    Confirm patched version is live in production

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

Affected packages

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

References

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