CVE-2026-74905: siyuan · Server-Side Request Forgery (SSRF)
Affects siyuanSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium : upgrade to 3.7.4 when convenient.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 33% 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:N/VI:L/VA:N/SC:L/SI:L/SA:LExploitation evidence
Disclosed: evidence found.
CVE published 18 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 17 Nov 2026.
What to do
Upgrade siyuan and siyuan-note/siyuan to 3.7.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| siyuan-notesiyuan | Affected
| Fixed in
|
GitHubsiyuan-note/siyuanpkg:github/siyuan-note/siyuanOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in SiYuan version 3.7.4. Users should upgrade to version 3.7.4 or later to remediate this SSRF vulnerability. Until upgraded, avoid enabling SafeMode or restrict access to proxy endpoints to trusted users only.
Description
SiYuan note-taking software versions before 3.7.4 contain a server-side request forgery (SSRF) vulnerability in the isPrivateIP function. This function fails to recognize certain IPv6 transition addresses that embed private IPv4 destinations, allowing authenticated attackers to bypass SSRF protections in SafeMode. Exploitation can occur via network forward proxy, WebSocket proxy, or SSE proxy endpoints, enabling attackers to access internal services and cloud metadata endpoints such as 169.254.169.254. The vulnerability allows full-read SSRF, potentially leading to credential theft and internal network reconnaissance.