# CVE-2026-93922: SiYuan through 3.8.4 Stored XSS via notebook names

> Attackers can execute arbitrary code via stored XSS in notebook names within the SiYuan note-taking application.

- **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:** 18 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-8c2m-33v9-vvqm, GHSA-jfm6-64hf-4hh9

## What is CVE-2026-93922?

CVE-2026-93922 is a high-severity cross-site scripting vulnerability in siyuan-note siyuan, published on 18 Sep 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 through 3.8.4 renders notebook names as raw HTML in the Daily Note picker dialog without escaping, allowing stored cross-site scripting in the Electron renderer. Attackers can create notebooks with HTML payloads in names that execute JavaScript with Node.js access when the picker opens, enabling operating system command execution.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-93922 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93922 is a high-severity cross-site scripting vulnerability in siyuan-note siyuan, published on 18 Sep 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-93922 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-93922/ (Markdown: https://insights.sbomify.com/CVE-2026-93922/index.md)
```

## Sources

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

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