SiYuan versions before v3.7.4 fail to mask sensitive configuration fields in the /api/system/getConf endpoint, allowing anonymous or publish-reader users to obtain the session-cookie signing key, OS username via pandoc path, and encrypted-notebook key material. Attackers can forge and tamper with session cookies to impersonate users, and on instances without access-auth codes configured, escalate to administrator privileges.
CVE-2026-72793
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
- 16%
- KEV
- Not listed
Published
August 12, 2026
Last Modified
August 14, 2026
Advisory Details (2)
Auto-updated Aug 12, 2026SiYuan before v3.7.4 Information Disclosure via /api/system/getConf | Advisories | VulnCheck
https://www.vulncheck.com/advisories/siyuan-before-information-disclosure-via-api-system-getconfNon-administrator responses from /api/system/getConf omit three secrets that the configuration-export path explicitly strips, disclosing the session-cookie signing key and the OS username to anonymous readers · Advisory · siyuan-note/siyuan · GitHub
https://github.com/siyuan-note/siyuan/security/advisories/GHSA-h4v5-crx2-3cv4Vendor Advisories for CVE-2026-72793(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 34× in last 7d / 39× 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-20 08:13 UTCGHSA enrichment
- 2026-08-19 19:18 UTCEG score recompute
- 2026-08-19 19:18 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 06:21 UTCGHSA enrichment
- 2026-08-18 17:19 UTCEG score recompute
- 2026-08-18 17:18 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 03:49 UTCGHSA enrichment
- 2026-08-17 14:54 UTCEG score recompute
- 2026-08-17 14:54 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 01:59 UTCEG score recompute
- 2026-08-17 01:59 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 13:04 UTCEG score recompute
- 2026-08-16 13:04 UTCGHSA enrichment
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-16 00:09 UTCGHSA enrichment
- 2026-08-15 11:14 UTCEG score recompute
- 2026-08-15 11:14 UTCGHSA enrichment
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 22:18 UTCEG score recompute
Show 14 moreShow fewer
- 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 11:05 UTCGHSA enrichment
- 2026-08-13 22:10 UTCEG score recompute
- 2026-08-13 22:10 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 09:15 UTCEG score recompute
- 2026-08-13 09:15 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-522
- CVE-2013-7055EG 9.8EPSS p94CRITICAL
- CVE-2013-7052EG 9.8EPSS p98CRITICAL
- CVE-2014-3445EG 9.8EPSS p92CRITICAL
- CVE-2014-5381EG 9.8EPSS p94CRITICAL
- CVE-2014-5093EG 9.8CRITICAL
- CVE-2016-4401EG 9.8CRITICAL
- CVE-2017-16714EG 9.8CRITICAL
- CVE-2017-11510EG 9.8CRITICAL
- CVE-2017-17106EG 9.8EPSS p96CRITICAL
- CVE-2017-3192EG 9.8EPSS p98CRITICAL
Frequently asked(5)
What is CVE-2026-72793?
When was CVE-2026-72793 disclosed?
Is CVE-2026-72793 actively exploited?
What is the CVSS score of CVE-2026-72793?
How do I remediate CVE-2026-72793?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-72793
Is Your Infrastructure Affected by CVE-2026-72793?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.