CVE-2026-85175
SiYuan <=3.8.1 exposes TLS/CA private keys via API, enabling MITM and certificate forging.
Is CVE-2026-85175 being exploited?
Not confirmed. CVE-2026-85175 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.19% probability of exploitation in the next 30 days.
How severe is CVE-2026-85175?
CVE-2026-85175 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-85175?
Yes. A fix has been recorded for CVE-2026-85175. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-85175 affect?
CVE-2026-85175 affects SiYuan <= 3.8.1, /api/file/getFile handler, conf/key.pem, conf/ca.key. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-85175?
Upgrade to SiYuan v3.8.2, rotate TLS and CA keys, revoke/reissue certs, and audit access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated users or default no-auth instances can download conf/key.pem and conf/ca.key, allowing HTTPS decryption and forging trusted certificates.
Immediate action required
- affected< 3.8.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.