# CVE-2026-59855: SiYuan: Store XSS To Rce via Asset.render

> Attackers can execute arbitrary OS commands via stored XSS in SiYuan by injecting malicious JavaScript into asset paths rendered in the Electron interface.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** No
- **Published:** 9 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-w3gq-5j72-36vc

## What is CVE-2026-59855?

CVE-2026-59855 is a high-severity cross-site scripting vulnerability in siyuan-note siyuan, published on 9 Jul 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.1, Asset.render in app/src/asset/index.ts interpolates the unsanitized this.path value into HTML assigned to innerHTML, allowing a crafted asset link containing a double quote to break out of the src attribute, inject an event handler, and execute JavaScript that can run OS commands in the Electron renderer. This issue is fixed in versions 3.7.1-alpha.2 and 3.7.1.

Weakness: CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page)

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


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

No fix has been published for CVE-2026-59855 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-59855 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59855 is a high-severity cross-site scripting vulnerability in siyuan-note siyuan, published on 9 Jul 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-59855 exists.

Affected product: siyuan-note siyuan. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-59855/ (Markdown: https://insights.sbomify.com/CVE-2026-59855/index.md)
```

## Sources

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

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