SiYuan before v3.7.4 fails to properly validate publish access for encrypted notebooks, treating them as publicly accessible by default. Anonymous readers can enumerate and retrieve fully decrypted document content from unlocked encrypted notebooks through the publish API without authentication or key material.
CVE-2026-72789
Score 8.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-12. 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
- 0%
- EPSS %ILE
- 22%
- KEV
- Not listed
Published
August 12, 2026
Last Modified
August 14, 2026
Advisory Details (2)
Auto-updated Aug 12, 2026SiYuan before v3.7.4 Authentication Bypass via Encrypted Notebooks | Advisories | VulnCheck
https://www.vulncheck.com/advisories/siyuan-before-authentication-bypass-via-encrypted-notebooksThe publish-access gate treats encrypted notebooks as publicly accessible by default, allowing anonymous readers to retrieve fully decrypted document content while a notebook is unlocked · Advisory · siyuan-note/siyuan · GitHub
https://github.com/siyuan-note/siyuan/security/advisories/GHSA-v684-q882-jgmqVendor Advisories for CVE-2026-72789(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 35× in last 7d / 44× 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-21 05:17 UTCEG score recompute
- 2026-08-21 05:17 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 17:44 UTCGHSA enrichment
- 2026-08-20 06:10 UTCGHSA enrichment
- 2026-08-19 18:36 UTCEG score recompute
- 2026-08-19 18:36 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 06:21 UTCGHSA enrichment
- 2026-08-18 18:45 UTCEG score recompute
- 2026-08-18 18:45 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 07:11 UTCGHSA enrichment
- 2026-08-17 19:38 UTCEG score recompute
- 2026-08-17 19:38 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 08:04 UTCGHSA enrichment
- 2026-08-16 20:31 UTCEG score recompute
- 2026-08-16 20:31 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 08:58 UTCEG score recompute
- 2026-08-16 08:58 UTCGHSA enrichment
- 2026-08-16 02:15 UTCEPSS rescore
Show 19 moreShow fewer
- 2026-08-15 21:25 UTCGHSA enrichment
- 2026-08-15 09:52 UTCEG score recompute
- 2026-08-15 09:52 UTCGHSA enrichment
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 22:18 UTCEG score recompute
- 2026-08-14 22:18 UTCGHSA enrichment
- 2026-08-14 22:04 UTCEG score recompute
- 2026-08-14 22:04 UTCGHSA enrichment
- 2026-08-14 17:09 UTCEG score recompute
- 2026-08-14 17:09 UTCGHSA enrichment
- 2026-08-14 06:59 UTCEG score recompute
- 2026-08-14 06:59 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 19:26 UTCGHSA enrichment
- 2026-08-13 07:53 UTCEG score recompute
- 2026-08-13 07:53 UTCGHSA enrichment
- 2026-08-12 20:20 UTCEG score recompute
- 2026-08-12 19:21 UTCEG score recompute
- 2026-08-12 19:20 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(5)
What is CVE-2026-72789?
When was CVE-2026-72789 disclosed?
Is CVE-2026-72789 actively exploited?
What is the CVSS score of CVE-2026-72789?
How do I remediate CVE-2026-72789?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-72789
Is Your Infrastructure Affected by CVE-2026-72789?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.