CVE-2026-65605 siyuan-note CVE debrief

Who should care

Defenders and administrators of SiYuan deployments should assess exposure and prioritize verification and remediation. They should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. Additionally, they should plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Why it matters

Defenders should prioritize verifying and upgrading to SiYuan version 3.7.2 or later, and assess exposure in their deployment contexts, as the vulnerability allows for stored cross-site scripting and potential escalation to arbitrary command execution.

• Potential escalation to arbitrary command execution
• Stored cross-site scripting vulnerability
• Execution of injected script when database is viewed

Technical summary

The vulnerability exists in SiYuan before v3.7.2 in Attribute View (database) cell rendering. A Template column value is rendered as HTML via text/template without auto-escaping, allowing for payloads like <img src=x onerror=...> to be stored unescaped and later inserted into the page via innerHTML, executing when the database is viewed. The desktop renderer runs with nodeIntegration enabled, allowing injected script to reach require and escalate to arbitrary command execution. This vulnerability allows for stored cross-site scripting and potential escalation to arbitrary command execution.

Defensive priority

Defenders should prioritize verifying and upgrading to SiYuan version 3.7.2 or later, and assess exposure in their deployment contexts.

Recommended defensive actions

• Verify and upgrade to SiYuan version 3.7.2 or later
• Assess exposure in deployment contexts
• Monitor for potential exploitation attempts
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its CVSS score of 9.4 and severity of CRITICAL. The vulnerability allows for stored cross-site scripting and potential escalation to arbitrary command execution.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.