# CVE-2026-44586: SiYuan: Bazaar marketplace renders unescaped package author metadata, allowing XSS and Electron code execution

> Attackers can execute arbitrary code on the host via stored XSS in the Bazaar marketplace due to unescaped metadata and insecure Electron configuration.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A: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:** No
- **Published:** 14 May 2026
- **Updated:** 14 May 2026
- **Also known as:** GHSA-x6wf-w2rg-2gw9

## What is CVE-2026-44586?

CVE-2026-44586 is a high-severity 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. From 2.1.12 to before 3.7.0. SiYuan's Bazaar marketplace renders package author metadata from the public bazaar stage feed into HTML without escaping. In the desktop app this becomes stored XSS, and because SiYuan's Electron windows are created with nodeIntegration: true and contextIsolation: false, a successful payload can call Node.js APIs and execute code on the host. 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)

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


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

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

## Is CVE-2026-44586 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44586 is a high-severity 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-44586 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-44586/ (Markdown: https://insights.sbomify.com/CVE-2026-44586/index.md)
```

## Sources

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

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