# CVE-2026-44670: SiYuan: Stored XSS via Attribute View name to Electron renderer RCE in SiYuan

> Stored XSS in SiYuan allows remote code execution via Electron renderer due to unsafe HTML injection and insecure browser settings.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 May 2026
- **Updated:** 15 May 2026
- **Also known as:** GHSA-2h64-c999-c9r6, GO-2026-4992

## What is CVE-2026-44670?

CVE-2026-44670 is a critical cross-site scripting vulnerability in siyuan-note siyuan, published on 14 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

SiYuan is an open-source personal knowledge management system. Prior to 3.7.0, the kernel stores Attribute View (AV / database) names without any HTML escape, then a render template uses raw strings.ReplaceAll(tpl, "${avName}", nodeAvName) to embed the name in HTML before pushing to all clients via WebSocket. Three independent client paths (render.ts:120 → outerHTML, Title.ts:401 → innerHTML, transaction.ts:559 → innerHTML) consume the value without escaping. Because the main BrowserWindow runs nodeIntegration:true, contextIsolation:false, webSecurity:false (app/electron/main.js:407-411), HTML injection in the renderer becomes Node.js code execution. This vulnerability is fixed in 3.7.0.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-1188 (Initialization of a Resource with an Insecure Default)

## Which versions are affected by CVE-2026-44670?

3 open source packages ship an affected version, including github.com/siyuan-note/siyuan/kernel.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260512140701-d7b77d945e0d |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260512140701-d7b77d945e0d |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260512140701-d7b77d945e0d |

## How do I fix CVE-2026-44670?

Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260512140701-d7b77d945e0d or later.

## Is CVE-2026-44670 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44670 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44670 and fix it if it is affected.

What it is: CVE-2026-44670 is a critical cross-site scripting vulnerability in siyuan-note siyuan, published on 14 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44670 exists.

Affected packages and fixed versions:
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260512140701-d7b77d945e0d
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260512140701-d7b77d945e0d
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260512140701-d7b77d945e0d

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44670/ (Markdown: https://insights.sbomify.com/CVE-2026-44670/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44670
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44670
- OSV: https://osv.dev/vulnerability/CVE-2026-44670

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44670/
Summaries are generated and may contain mistakes; the official description above is the record.