CVE-2026-72793
Unauthenticated endpoint exposes signing and encryption keys enabling impersonation and admin takeover.
Is CVE-2026-72793 being exploited?
Not confirmed. CVE-2026-72793 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.24% probability of exploitation in the next 30 days.
How severe is CVE-2026-72793?
CVE-2026-72793 is rated Critical with a CVSS score of 9.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-72793?
Yes. A fix has been recorded for CVE-2026-72793. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72793 affect?
CVE-2026-72793 affects SiYuan < v3.7.4, /api/system/getConf endpoint, SiYuan server instances. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72793?
Upgrade to v3.7.4+, rotate session and notebook keys, restrict API access and audit auth-code usage.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Disclosure of session signing key and notebook keys lets attackers forge session cookies to impersonate users and escalate to admin on unprotected instances.
Immediate action required
- affected< 3.7.4
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.