# SiYuan has incomplete fix for CVE-2026-33066: XSS

Advisory record · `GHSA-8q5w-mmxf-48jg`

- **Identifiers:** `GHSA-8q5w-mmxf-48jg` · `CVE-2026-40922` · `GO-2026-5260`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-79](https://cwe.mitre.org/data/definitions/79.html)
- **Tags:** [Cross-site scripting (XSS)](https://agentprime.io/advisories/tag/xss.md)
- **Published:** 14 Apr 2026
- **Updated:** 8 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 14 Apr 2026, 23:12 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/siyuan-note/siyuan/kernel` (Go): affected `<0.0.0-20260414013942-62eed37a3263`; fixed in `0.0.0-20260414013942-62eed37a3263`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> SiYuan's Go kernel package (github.com/siyuan-note/siyuan/kernel) versions before 0.0.0-20260414013942-62eed37a3263 are affected by stored cross-site scripting in bazaar package README rendering. A malicious bazaar package author can embed an iframe with a srcdoc attribute containing script, which runs in the Electron context when other users view the package in the marketplace. Upgrade to 0.0.0-20260414013942-62eed37a3263 or later.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.3 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0027, the 18th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:05 UTC: First seen by agentprime
- 31 Oct 2026, 15:05 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-8q5w-mmxf-48jg)

## Sources

- [GitHub Advisory Database: GHSA-8q5w-mmxf-48jg](https://github.com/advisories/GHSA-8q5w-mmxf-48jg)
- [OSV: GHSA-8q5w-mmxf-48jg](https://osv.dev/vulnerability/GHSA-8q5w-mmxf-48jg)
- <https://github.com/siyuan-note/siyuan/security/advisories/GHSA-8q5w-mmxf-48jg>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-33066>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-40922>
- <https://github.com/siyuan-note/siyuan/commit/b382f50e1880ed996364509de5a10a72d7409428>
- <https://github.com/advisories/GHSA-4663-4mpg-879v>
- <https://github.com/siyuan-note/siyuan>
- <https://github.com/siyuan-note/siyuan/releases/tag/v3.6.4>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-8q5w-mmxf-48jg>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-8q5w-mmxf-48jg/>. Everything for agents: <https://agentprime.io/llms.txt>.
