SiYuan versions before v3.7.3 contain an information disclosure vulnerability in the getHeadingDeleteTransaction, getHeadingLevelTransaction, and getHeadingInsertTransaction endpoints that return rendered block DOM without publish-access checks. Anonymous readers or publish RoleReader tokens can supply a heading block ID to read full rendered content of publish-disabled documents that should be restricted.
CVE-2026-68587
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
- 70(Attend)EG Risk 70/100SSVC: Attend
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%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - 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 Information Disclosure via getHeading*Transaction | Advisories | VulnCheck
https://www.vulncheck.com/advisories/siyuan-before-information-disclosure-via-getheading-transactionFull-content disclosure of publish-disabled documents via getHeading*Transaction endpoints (publish mode): reader-reachable rendered DOM with no publish-access check · Advisory · siyuan-note/siyuan · GitHub
https://github.com/siyuan-note/siyuan/security/advisories/GHSA-69mh-gvh4-8gp7Vendor Advisories for CVE-2026-68587(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 6× in last 7d / 6× 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 16:36 UTCEG score recompute
- 2026-08-03 16:36 UTCGHSA enrichment
- 2026-08-03 15:28 UTCEG score recompute
- 2026-08-03 14:33 UTCEG score recompute
- 2026-08-03 13:36 UTCEG score recompute
- 2026-08-03 13:33 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
- CVE-2013-3960EG 9.9CRITICAL
- CVE-2015-10143EG 9.8CRITICAL
- CVE-2016-11036EG 9.8CRITICAL
- CVE-2018-11541EG 9.8CRITICAL
- CVE-2011-4183NVD 6.5EG 9.8CRITICAL
- CVE-2018-10251EG 9.8EPSS p91CRITICAL
- CVE-2018-1217EG 9.8EPSS p99CRITICAL
- CVE-2018-0015EG 9.8CRITICAL
- CVE-2017-12582EG 9.8CRITICAL
- CVE-2017-1000056EG 9.8CRITICAL
Frequently asked(4)
What is CVE-2026-68587?
When was CVE-2026-68587 disclosed?
What is the CVSS score of CVE-2026-68587?
How do I remediate CVE-2026-68587?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-68587
Is Your Infrastructure Affected by CVE-2026-68587?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.