Quick answers
- Is CVE-2026-39846 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-39846 being exploited in the wild.
- How severe is CVE-2026-39846?
- Critical severity, with a CVSS score of 9, published 7 April 2026.
- Which products and versions are affected?
- github.com/siyuan-note/siyuan/kernel (Go) SEMVER:introduced=0,fixed=0.0.0-20260407035653-2f416e5253f1; SiYuan < 3.6.4.
- Is there a fix for CVE-2026-39846?
- Yes. github.com/siyuan-note/siyuan/kernel (Go): upgrade to 0.0.0-20260407035653-2f416e5253f1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-39846 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-39846?
- Check whether you run github.com/siyuan-note/siyuan/kernel (Go) or SiYuan at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- github.com/siyuan-note/siyuan/kernel (Go): upgrade to 0.0.0-20260407035653-2f416e5253f1 or later
go get github.com/siyuan-note/siyuan/kernel@v0.0.0-20260407035653-2f416e5253f1
Technical details
A stored Cross-Site Scripting (XSS) vulnerability exists in the SiYuan Electron desktop client due to improper neutralization of table caption content. The application stores table captions without escaping and subsequently unescapes them into the rendered HTML DOM. Because the Electron renderer is configured with 'nodeIntegration' enabled and 'contextIsolation' disabled, an attacker can leverage this XSS sink to execute arbitrary Node.js APIs, such as 'child_process.exec'. The attack is delivered by importing a crafted '.sy.zip' note into a shared workspace; when a victim syncs and opens the note, the payload executes in the context of the logged-in user. This issue is resolved in version 3.6.4.
Affected products
- siyuan-note SiYuan < 3.6.4
Identifiers
- CVE-2026-39846
- GHSA-phhp-9rm9-6gr2
- GO-2026-5540
Timeline
- 2026-04-07: disclosed
- 2026-04-07: advisory
- 2026-04-07: patched: Fixed in version 3.6.4