CVE-2026-105205 siyuan-note CVE debrief

Who should care

Defenders and administrators of SiYuan instances, especially those with sensitive documents, should assess their exposure and potential impact of information disclosure. They should prioritize verifying exposure of SiYuan instances and review and update SiYuan instances to version 3.8.5 or later if possible.

Why it matters

CVE-2026-105205 is an information disclosure vulnerability in SiYuan before version 3.8.5 that allows publish-mode readers to learn backlink block IDs and reference counts from password-protected and publish-disabled documents. Defenders should prioritize verifying exposure of SiYuan instances, especially those with sensitive documents, and assess the impact of potential information disclosure.

• Verify exposure of SiYuan instances to potential information disclosure
• Assess the impact of potential information disclosure on sensitive documents
• Review and update SiYuan instances to version 3.8.5 or later if possible

Technical summary

The vulnerability allows publish-mode readers to learn backlink block IDs and reference counts from password-protected and publish-disabled documents by querying a published document. This can be done by sending POST requests to /api/block/getDocInfo or getDocsInfo for a published document ID. The vulnerability affects SiYuan before version 3.8.5 and has a CVSS score of 6.9 with a severity of MEDIUM. Defenders should prioritize verifying exposure of SiYuan instances, especially those with sensitive documents, and assess the impact of potential information disclosure.

Defensive priority

Defenders should prioritize verifying exposure of SiYuan instances, especially those with sensitive documents, and assess the impact of potential information disclosure.

Recommended defensive actions

• Verify SiYuan instance exposure, especially those with sensitive documents
• Assess the impact of potential information disclosure
• Review and update SiYuan instances to version 3.8.5 or later if possible
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but the corpus lacks specific information on affected versions, exploitation, and remediation. The vulnerability allows publish-mode readers to learn backlink block IDs and reference counts from password-protected and publish-disabled documents. Limited source detail is available, so defenders should verify exposure and assess potential impact with explicit evidence-limit language and defensive verification tasks.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.