Quick answers
- Is CVE-2026-34449 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-34449 being exploited in the wild.
- How severe is CVE-2026-34449?
- Critical severity, with a CVSS score of 9.6, published 31 March 2026.
- Which products and versions are affected?
- github.com/siyuan-note/siyuan/kernel (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=3.6.2; SiYuan < 3.6.2.
- Is there a fix for CVE-2026-34449?
- Yes. github.com/siyuan-note/siyuan/kernel (Go): upgrade to 3.6.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-34449 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-34449?
- 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 3.6.2 or later
go get github.com/siyuan-note/siyuan/kernel@v3.6.2
Technical details
SiYuan (prior to v3.6.2) implements a permissive Cross-Origin Resource Sharing (CORS) policy in 'kernel/server/serve.go' that sets 'Access-Control-Allow-Origin: *' and 'Access-Control-Allow-Private-Network: true'. This configuration allows external websites to bypass Chrome's Private Network Access protections and make authenticated requests to the local SiYuan API (typically on port 6806) using the user's session cookies. An attacker can use the '/api/snippet/setSnippet' endpoint to inject malicious JavaScript. Because SiYuan is built on Electron with Node.js integration enabled, this injected code executes with full operating system privileges the next time the UI is loaded. The vulnerability also allows for immediate data exfiltration of notes and API tokens.
Affected products
- siyuan-note SiYuan < 3.6.2
Identifiers
- CVE-2026-34449
- GHSA-68p4-j234-43mv
- GO-2026-5171
Timeline
- 2026-03-18: other: Issue reported to vendor
- 2026-03-28: advisory: GitHub Security Advisory published
- 2026-03-31: patched: Version 3.6.2 released
- 2026-03-31: disclosed: CVE-2026-34449 published