CVE-2026-34448 — kernel
CRITICALCVE-2026-34448 is a critical-severity (CVSS 9) Cross-site Scripting (XSS) vulnerability in github.com/siyuan-note/siyuan/kernel. A fix is available for github.com/siyuan-note/siyuan/kernel — see the affected versions and patch details below.
SiYuan: Stored XSS in Attribute View gallery/kanban cover rendering allows arbitrary command execution in the desktop client
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-34448.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/siyuan-note/siyuan/kernelReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Summary
An attacker who can place a malicious URL in an Attribute View mAsse field can trigger stored XSS when a victim opens the Gallery or Kanban view with “Cover From -> Asset Field” enabled. The vulnerable code accepts arbitrary http(s) URLs without extensions as images, stores the attacker-controlled string in coverURL, and injects it directly into an <img src="..."> attribute without escaping. In the Electron desktop client, the injected JavaScript executes with nodeIntegration enabled and contextIsolation disabled, so the XSS reaches arbitrary OS command execution under the victim’s account.
Details
The vulnerable flow is:
IsPossiblyImage(assetPath)accepts arbitraryhttp(s)URLs without validating that they are safe image URLs.- When an Attribute View card uses
Cover From -> Asset Field, the application copiesasset.Contentdirectly intogalleryCard.CoverURL / kanbanCard.CoverURL. - The front-end renderer inserts
coverURLdirectly into<img src="${getCompressURL(item.coverURL)}">without escaping quotes or other attribute-breaking characters. - A payload such as
https://example.com/" onerror="require('child_process').exec('calc')breaks out of thesrcattribute and adds an attacker-controlledonerrorhandler. When the image fails to load, the injected JavaScript runs in the Electron renderer. Because the desktop app enablesnodeIntegration: trueand disablescontextIsolationandwebSecurity, that JavaScript can access Node.js APIs and execute system commands.
PoC
- Install Electron Desktop app.
- Create a database / Attribute View with an mAsset column and add at least one row.
- Add any legitimate image to that mAsset field so the entry is stored as type image.
- Switch the view to Gallery or Kanban. 5.Set Cover From to Asset Field and choose the mAsset column.
- Edit the existing image asset entry and replace its link with the following payload:
https://example.com/" onerror="require('child_process').exec('calc')
- Save the change and reopen or refresh the Gallery / Kanban view.
- Observe that the rendered HTML contains an injected onerror handler and the Calculator application starts on Windows.
Example rendered output:
<img loading="lazy" class="av__gallery-img" src="https://example.com/" onerror="require('child_process').exec('calc')">
Impact
An attacker can store malicious content in a database asset field and execute arbitrary JavaScript when another user opens the affected Gallery or Kanban view. In the desktop client, that JavaScript has access to Node.js APIs, so the impact is not limited to browser-context XSS. The payload executes OS commands with the victim’s local user privileges, which turns this into remote code execution on the desktop application once the malicious content is delivered and rendered.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/siyuan-note/siyuan/kernel | all versions | 3.6.2go get github.com/siyuan-note/siyuan/kernel@v3.6.2 |
Affected Products
siyuanb3logDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/siyuan-note/siyuan/kernel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/siyuan-note/siyuan/kernel to 3.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-34448 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is CVE-2026-34448 in your dependencies?
Find it across Go, including transitive dependencies.