# CVE-2026-82653: SiYuan before v3.8.1 Stored XSS via confirmDialog

> Attackers can execute arbitrary scripts in users' browsers by submitting malicious package or notebook names in SiYuan.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Aug 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-hvwp-43j9-4xgf, GHSA-pxmq-4h62-hcr8

## What is CVE-2026-82653?

CVE-2026-82653 is a critical cross-site scripting vulnerability in siyuan-note siyuan, published on 30 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

SiYuan before v3.8.1 contains a stored cross-site scripting vulnerability in confirmDialog() where unescaped package names and notebook names are interpolated directly into innerHTML assignments. Attackers can submit malicious bazaar packages with HTML/script payloads in the name field that execute in users' browsers when uninstalling packages or unlocking encrypted notebooks.

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

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


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

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

## Is CVE-2026-82653 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82653 is a critical cross-site scripting vulnerability in siyuan-note siyuan, published on 30 Aug 2026. Any signed-in user can exploit it over the network, 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-82653 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-82653/ (Markdown: https://insights.sbomify.com/CVE-2026-82653/index.md)
```

## Sources

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

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