SiYuan before v3.7.3 fails to apply publish-access filters to the getBacklinkDoc and getBackmentionDoc content endpoints (/api/ref/getBacklinkDoc and /api/ref/getBackmentionDoc). While the corresponding backlink list endpoints filter publish-forbidden documents, the content endpoints (gated only by CheckAuth) do not. A publish-mode reader — including an anonymous reader when publish Basic Auth is disabled — can call these endpoints directly with a publish-forbidden document's ID to retrieve its rendered DOM content and to determine whether the document references a given block (a reference-existence oracle).
CVE-2026-68586
Score 8.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-03. a secondary CVSS source baseline 8.6; sources differ by 0.0.
- 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.6
- EG Score
- 8.6(high)
- EG Risk
- 54(Track)EG Risk 54/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 computedSeverity86% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 3, 2026
Last Modified
August 3, 2026
Advisory Details (2)
Auto-updated Aug 3, 2026SiYuan before v3.7.3 Content Disclosure via getBacklinkDoc | Advisories | VulnCheck
https://www.vulncheck.com/advisories/siyuan-before-content-disclosure-via-getbacklinkdocCross-boundary content disclosure via getBacklinkDoc/getBackmentionDoc (publish mode): reader-reachable rendered DOM of publish-forbidden docs; sibling list endpoints are filtered · Advisory · siyuan-note/siyuan · GitHub
https://github.com/siyuan-note/siyuan/security/advisories/GHSA-36v8-mpjm-8j5rVendor Advisories for CVE-2026-68586(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× 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-08-03 17:40 UTCEG score recompute
- 2026-08-03 17:40 UTCGHSA enrichment
- 2026-08-03 16:19 UTCEG score recompute
- 2026-08-03 16:19 UTCGHSA enrichment
- 2026-08-03 14:33 UTCEG score recompute
- 2026-08-03 13:36 UTCEG score recompute
- 2026-08-03 13:33 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-68586?
When was CVE-2026-68586 disclosed?
What is the CVSS score of CVE-2026-68586?
How do I remediate CVE-2026-68586?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-68586
Is Your Infrastructure Affected by CVE-2026-68586?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.