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.
CVE-2026-32110
This high-severity CVE scores 8.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.3
- EG Score
- 8.3(low)
- EG Risk
- 42(Track)EG Risk 42/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity83% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 20%
- KEV
- Not listed
Published
March 11, 2026
Last Modified
June 17, 2026
References (1)
- security-advisories@githubhttps://github.com/siyuan-note/siyuan/security/advisories/GHSA-56cv-c5p2-j2wg
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-27 13:37 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-32110?
When was CVE-2026-32110 disclosed?
Is CVE-2026-32110 actively exploited?
What is the CVSS score of CVE-2026-32110?
How do I remediate CVE-2026-32110?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-32110
Is Your Infrastructure Affected by CVE-2026-32110?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.