Skip to content
Fencer Vulns
high 8.3

CVE-2026-32110 json

SiYuan has a Full-Read SSRF via /api/network/forwardProxy

published 2026-03-11 7 mo ago modified 2026-11-05 3 d ago also GHSA-56cv-c5p2-j2wg , GO-2026-4685 , EUVD-2026-11381

cvss
8.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 31%
public exploits
0
none known

Summary

SiYuan is a personal knowledge management system. Prior to 3.6.0, the /api/network/forwardProxy endpoint allows authenticated users to make arbitrary HTTP requests from the server. The endpoint accepts a user-controlled URL and makes HTTP requests to it, returning the full response body and headers. There is no URL validation to prevent requests to internal networks, localhost, or cloud metadata services. This vulnerability is fixed in 3.6.0.

Patch / fix

  • go github.com/siyuan-note/siyuan/kernel 3.6.0
  • b3log siyuan 3.6.0
  • govulncheck-vulndb openSUSE Leap 15.6 0.0.20260317T205859-150000.1.152.1

suse advisories SUSE-SU-2026:1042-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
7 mo ago

Exploit prediction

0.38% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/siyuan-note/siyuan/security/advisories/GHSA-56cv-c5p2-j2wg referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 8.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
GitHub 3.1 8.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

Affected packages

ecosystem package affected fixed in
go github.com/siyuan-note/siyuan/kernel
<3.6.0
all versions
3.6.0

Affected products

  • siyuan-note siyuan

Classification

Weakness
  • CWE-918 Server-Side Request Forgery

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.