# SiYuan has a SVG Sanitizer Bypass via \`\<animate>\` Element — Unauthenticated XSS

Advisory record · `GHSA-5hc8-qmg8-pw27`

- **Identifiers:** `GHSA-5hc8-qmg8-pw27` · `CVE-2026-31807` · `GO-2026-4667`
- **State:** Confirmed
- **Severity:** CVSS 6.4 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:** 10 Mar 2026
- **Updated:** 23 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 10 Mar 2026, 23:49 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-20260310025236-297bd526708f`; fixed in `0.0.0-20260310025236-297bd526708f`

## Machine-written summary

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

> SiYuan (Go module github.com/siyuan-note/siyuan/kernel) versions up to 0.0.0-20260310025236-297bd526708f contain an SVG sanitizer bypass that allows cross-site scripting through the animate and set SVG elements. An attacker can send a crafted link to a user, and when the user opens it, JavaScript runs in the SiYuan origin with access to authenticated APIs. The source lists the fixed version as 0.0.0-20260310025236-297bd526708f, so upgrade to that version. The source gives no other workaround.

Written 7 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

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

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

## Timeline

- 31 Oct 2026, 15:09 UTC: First seen by agentprime
- 31 Oct 2026, 15:09 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-5hc8-qmg8-pw27)

## Sources

- [GitHub Advisory Database: GHSA-5hc8-qmg8-pw27](https://github.com/advisories/GHSA-5hc8-qmg8-pw27)
- [OSV: GHSA-5hc8-qmg8-pw27](https://osv.dev/vulnerability/GHSA-5hc8-qmg8-pw27)
- <https://github.com/siyuan-note/siyuan/security/advisories/GHSA-5hc8-qmg8-pw27>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-31807>
- <https://github.com/siyuan-note/siyuan>
- <https://github.com/siyuan-note/siyuan/releases/tag/v3.5.10>

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-5hc8-qmg8-pw27>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-5hc8-qmg8-pw27/>. Everything for agents: <https://agentprime.io/llms.txt>.
