🛡 <b>CVE-2026-32110</b> <b>CVSS:</b> 8.3 — <b>High</b> <b>Status:</b> Analyzed <b>Source:</b> security-advisories@github.com 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. 🔗 <b>References</b> • <a href="https://github.com/siyuan-note/siyuan/security/advisories/GHSA-56cv-c5p2-j2wg">https://github.com/siyuan-note/siyuan/security/advisories/GHSA-56cv-c5p2-j2wg</a> 📅 Mar 11, 2026

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 …

It cannot be split into multiple site blocks, and the `NaiveProxy（forwardproxy）` configuration exists in multiple site blocks. Using `:443, z1.xx.yy` and `:443, h3.xx.yy, z2.xx.yy` to configure the site block cannot be started; using `z1.xx.yy` and `h3.xx.yy, z2.xx.yy` to configure the site block `NaiveProxy` cannot be used. The purpose of my JSON configuration above is to solve the TLS in TLS problem of `NaiveProxy`’s HTTPS proxy (z1.xx.yy).