Skip to main content
VulnerabilityPublished

CVE-2026-45371: siyuan · Improper Authorization

Affects siyuanSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.2 High : upgrade to 3.7.0 soon.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 4.0 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.7.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade siyuan and siyuan-note/siyuan to 3.7.0.

Affected software

ProductAffectedFixed in
siyuan-notesiyuanAffected
  • <3.7.0
Fixed in
  • 3.7.0
GitHubsiyuan-note/siyuanpkg:github/siyuan-note/siyuanOther threatsAffected
  • <3.7.0
Fixed in
  • 3.7.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade SiYuan to version 3.7.0 or later, where this improper authorization vulnerability has been fixed. Until then, restrict access to the affected APIs to trusted users only and avoid exposing publish-mode Reader roles to untrusted parties. Patch status is not explicitly confirmed in the advisory, but the vendor fixed the issue in version 3.7.0.

Description

SiYuan versions prior to 3.7.0 contain an improper authorization vulnerability where certain publish-mode Reader roles can modify server-side configuration and SQL index data via eight APIs that lack sufficient authorization checks. These APIs only require basic authentication but omit stricter admin or readonly role checks, allowing unauthorized mutation of critical state files. This vulnerability is addressed in version 3.7.0.

References

Community reviews

Loading reviews…