CVE-2026-29183 — AI Deep Analysis Summary

Q: What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: Reflected XSS in SiYuan Note. 📉 **Consequences**: Arbitrary JS execution, API abuse, and sensitive data leakage via crafted links.

Q: Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: CWE-79. The `/api/icon/getDynamicIcon` endpoint fails to escape attacker-controlled `content` in SVG output. 🐛 **Flaw**: Unsafe rendering logic for `type=8`.

Q: Who is affected? (Versions/Components)

👥 **Affected**: SiYuan Note versions **< 3.5.9**. 📦 **Component**: Dynamic Icon API endpoint.

Q: What can hackers do? (Privileges/Data)

💀 **Attacker Actions**: Execute JS in victim's browser. 📂 **Impact**: Perform authenticated API operations & steal sensitive user data.

Q: Is exploitation threshold high? (Auth/Config)

🔓 **Threshold**: Low. ⚠️ **Auth**: Unauthenticated vector. 🖱️ **UI**: Requires User Interaction (clicking a malicious link).

Q: Is there a public Exp? (PoC/Wild Exploitation)

🔍 **Exploit**: Yes. Public PoC available via Nuclei templates. 🌐 **Status**: Wild exploitation possible via crafted URLs.

Q: How to self-check? (Features/Scanning)

🔎 **Check**: Scan for `/api/icon/getDynamicIcon?type=8`. 🧪 **Test**: Inject payload into `content` param to trigger SVG rendering.

Q: Is it fixed officially? (Patch/Mitigation)

🛠️ **Fix**: Upgrade to SiYuan Note **v3.5.9+**. ✅ **Status**: Patched officially (GHSA-6865-qjcf-286f).

Q: What if no patch? (Workaround)

🚧 **Workaround**: If unpatched, restrict access to the icon API endpoint or implement strict input sanitization for SVG content.

Q: Is it urgent? (Priority Suggestion)

⚡ **Priority**: HIGH. 🚨 **Reason**: Unauthenticated, easy to exploit, and leads to data breach. Patch immediately!

Updated May 06, 2026 CVSS 9.3 · Critical

This is a summary of the AI-generated 10-question deep analysis. The full version (longer answers, follow-up Q&A, related CVEs) requires login. Read the full analysis →

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: Reflected XSS in SiYuan Note. 📉 **Consequences**: Arbitrary JS execution, API abuse, and sensitive data leakage via crafted links.

Q2Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: CWE-79. The `/api/icon/getDynamicIcon` endpoint fails to escape attacker-controlled `content` in SVG output. 🐛 **Flaw**: Unsafe rendering logic for `type=8`.

Q3Who is affected? (Versions/Components)

👥 **Affected**: SiYuan Note versions **< 3.5.9**. 📦 **Component**: Dynamic Icon API endpoint.

Q4What can hackers do? (Privileges/Data)

💀 **Attacker Actions**: Execute JS in victim's browser. 📂 **Impact**: Perform authenticated API operations & steal sensitive user data.

Q5Is exploitation threshold high? (Auth/Config)

🔓 **Threshold**: Low. ⚠️ **Auth**: Unauthenticated vector. 🖱️ **UI**: Requires User Interaction (clicking a malicious link).

Q6Is there a public Exp? (PoC/Wild Exploitation)

🔍 **Exploit**: Yes. Public PoC available via Nuclei templates. 🌐 **Status**: Wild exploitation possible via crafted URLs.

Q7How to self-check? (Features/Scanning)

🔎 **Check**: Scan for `/api/icon/getDynamicIcon?type=8`. 🧪 **Test**: Inject payload into `content` param to trigger SVG rendering.

Q8Is it fixed officially? (Patch/Mitigation)

🛠️ **Fix**: Upgrade to SiYuan Note **v3.5.9+**. ✅ **Status**: Patched officially (GHSA-6865-qjcf-286f).

Q9What if no patch? (Workaround)

🚧 **Workaround**: If unpatched, restrict access to the icon API endpoint or implement strict input sanitization for SVG content.

Q10Is it urgent? (Priority Suggestion)

⚡ **Priority**: HIGH. 🚨 **Reason**: Unauthenticated, easy to exploit, and leads to data breach. Patch immediately!

Continue exploring

Vulnerability detail Full AI analysis (login) siyuan-note CWE-79