CVE-2026-74868: siyuan · Improper Restriction of Excessive Authentication Attempts
Affects siyuanSource CVE Database V5
Not known to be exploited · CVSS 8.7 High : upgrade to 3.7.4 soon.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.7.4
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 16 Nov 2026.
What to do
Upgrade siyuan to 3.7.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| siyuan-notesiyuan | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, consider restricting network access to the Publish Service port (default TCP 6808) to trusted hosts only, or implement external rate limiting controls. Monitor for unusual authentication attempts on the Publish Service. Avoid exposing the Publish Service listener to untrusted networks.
Description
SiYuan versions before 3.7.4 have a vulnerability in the Publish Service Basic Auth implementation that allows unauthenticated remote attackers to perform unlimited password guesses due to lack of rate limiting or account lockout. This can lead to unauthorized access to published notes and notebooks.