CVE-2026-73607

MEDIUMPre-NVD 5.85.8—
EchelonGraph scoreHIGH confidence

Score 5.8 from GitHub Security Advisory published 2026-08-13. a secondary CVSS source baseline 5.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
5.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

SiYuan versions before v3.7.4 contain an information disclosure vulnerability in the /api/storage/getOutlineStorage endpoint that performs no authorization checks. Attackers can retrieve outline state including heading identifiers for any document by supplying its identifier, even for documents forbidden to the requester.

CVSS v3
5.8
EG Score
5.8(high)
EG Risk
57(Attend)
EG Risk 57/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 computed
Severity58% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

August 13, 2026

Last Modified

August 14, 2026

Advisory Details (2)

Auto-updated Aug 13, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

SiYuan before v3.7.4 Information Disclosure via getOutlineStorage | Advisories | VulnCheck

https://www.vulncheck.com/advisories/siyuan-before-information-disclosure-via-getoutlinestorage
github Patch Available🟡 PoC Available

Outline state for any document, including documents forbidden to readers, is returned by /api/storage/getOutlineStorage with no access check · Advisory · siyuan-note/siyuan · GitHub

https://github.com/siyuan-note/siyuan/security/advisories/GHSA-53fp-9jmv-227g

Vendor Advisories for CVE-2026-73607(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 25× in last 7d / 29× 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.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 15:08 UTCEG score recompute
  3. 2026-08-20 15:08 UTCGHSA enrichment
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-19 16:27 UTCGHSA enrichment
  6. 2026-08-18 17:50 UTCEG score recompute
  7. 2026-08-18 17:50 UTCGHSA enrichment
  8. 2026-08-18 13:49 UTCEPSS rescore
  9. 2026-08-18 13:49 UTCEPSS rescore
  10. 2026-08-17 19:13 UTCGHSA enrichment
  11. 2026-08-16 20:29 UTCEG score recompute
  12. 2026-08-16 20:29 UTCGHSA enrichment
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 02:15 UTCEPSS rescore
  16. 2026-08-15 21:54 UTCEG score recompute
  17. 2026-08-15 21:54 UTCGHSA enrichment
  18. 2026-08-15 01:31 UTCEPSS rescore
  19. 2026-08-14 23:19 UTCEG score recompute
  20. 2026-08-14 23:19 UTCGHSA enrichment
  21. 2026-08-14 22:39 UTCEG score recompute
  22. 2026-08-14 22:39 UTCGHSA enrichment
  23. 2026-08-14 17:08 UTCEG score recompute
  24. 2026-08-14 17:08 UTCGHSA enrichment
  25. 2026-08-14 11:08 UTCGHSA enrichment
Show 4 more
  1. 2026-08-13 12:33 UTCEG score recompute
  2. 2026-08-13 12:33 UTCGHSA enrichment
  3. 2026-08-13 11:42 UTCEG score recompute
  4. 2026-08-13 11:41 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-73607?
CVE-2026-73607 is a medium vulnerability published on August 13, 2026. SiYuan versions before v3.7.4 contain an information disclosure vulnerability in the /api/storage/getOutlineStorage endpoint that performs no authorization checks. Attackers can retrieve outline state including heading identifiers for any document by supplying its identifier, even for documents…
When was CVE-2026-73607 disclosed?
CVE-2026-73607 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73607 actively exploited?
CVE-2026-73607 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 90.5% of all scored CVEs.
What is the CVSS score of CVE-2026-73607?
CVE-2026-73607 has a CVSS v3 base score of 5.8 (NVD).
How do I remediate CVE-2026-73607?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73607, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-73607

Explore →

Is Your Infrastructure Affected by CVE-2026-73607?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs