SiYuan versions before v3.8.2 contain a path guard bypass vulnerability in the MCP file-access handler that uses case-sensitive matching on Linux filesystems. Attackers can read the protected publishAccess.json file by requesting case-variant paths like PublishAccess.json to disclose sensitive publish-access configuration and metadata.
CVE-2026-85580
Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-04. a secondary CVSS source baseline 6.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(high)
- EG Risk
- 45(Track)EG Risk 45/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 computedSeverity65% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 45%
- KEV
- Not listed
Published
September 4, 2026
Last Modified
September 8, 2026
Advisory Details (2)
Auto-updated Sep 4, 2026SiYuan before v3.8.2 Path Guard Bypass via Case Mismatch | Advisories | VulnCheck
https://www.vulncheck.com/advisories/siyuan-before-3.8.2-path-guard-bypass-via-case-mismatchLinux MCP publish-access path guard bypass exposes publishAccess.json · Advisory · siyuan-note/siyuan · GitHub
https://github.com/siyuan-note/siyuan/security/advisories/GHSA-mmgw-3mx9-cfwpVendor Advisories for CVE-2026-85580(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 20× in last 7d / 65× 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-09-25 03:12 UTCEG score recompute
- 2026-09-25 03:12 UTCGHSA enrichment
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-24 04:09 UTCEG score recompute
- 2026-09-24 04:09 UTCGHSA enrichment
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-23 05:16 UTCEG score recompute
- 2026-09-23 05:16 UTCGHSA enrichment
- 2026-09-22 16:01 UTCEPSS rescore
- 2026-09-22 06:22 UTCEG score recompute
- 2026-09-22 06:22 UTCGHSA enrichment
- 2026-09-21 21:09 UTCEPSS rescore
- 2026-09-21 07:29 UTCEG score recompute
- 2026-09-21 07:29 UTCGHSA enrichment
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-20 08:09 UTCEG score recompute
- 2026-09-20 08:09 UTCGHSA enrichment
- 2026-09-19 08:43 UTCEG score recompute
- 2026-09-19 08:43 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 09:42 UTCEG score recompute
- 2026-09-18 09:42 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-17 10:49 UTCEG score recompute
- 2026-09-17 10:49 UTCGHSA enrichment
Show 40 moreShow fewer
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-16 11:51 UTCEG score recompute
- 2026-09-16 11:51 UTCGHSA enrichment
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 12:58 UTCEG score recompute
- 2026-09-15 12:58 UTCGHSA enrichment
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-14 14:05 UTCEG score recompute
- 2026-09-14 14:05 UTCGHSA enrichment
- 2026-09-13 15:12 UTCGHSA enrichment
- 2026-09-12 16:19 UTCEG score recompute
- 2026-09-12 16:19 UTCGHSA enrichment
- 2026-09-11 17:26 UTCEG score recompute
- 2026-09-11 17:26 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 18:05 UTCEG score recompute
- 2026-09-10 18:05 UTCGHSA enrichment
- 2026-09-09 19:12 UTCEG score recompute
- 2026-09-09 19:12 UTCGHSA enrichment
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-08 20:19 UTCGHSA enrichment
- 2026-09-08 11:00 UTCEG score recompute
- 2026-09-08 11:00 UTCGHSA enrichment
- 2026-09-07 12:06 UTCEG score recompute
- 2026-09-07 12:06 UTCGHSA enrichment
- 2026-09-06 13:48 UTCEPSS rescore
- 2026-09-06 13:12 UTCEG score recompute
- 2026-09-06 13:12 UTCGHSA enrichment
- 2026-09-05 15:31 UTCEPSS rescore
- 2026-09-05 14:19 UTCEG score recompute
- 2026-09-05 14:19 UTCGHSA enrichment
- 2026-09-04 15:26 UTCEG score recompute
- 2026-09-04 15:26 UTCGHSA enrichment
- 2026-09-04 14:26 UTCEG score recompute
- 2026-09-04 14:25 UTCGHSA enrichment
- 2026-09-04 12:22 UTCEG score recompute
- 2026-09-04 11:34 UTCEG score recompute
- 2026-09-04 11:33 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-85580?
When was CVE-2026-85580 disclosed?
Is CVE-2026-85580 actively exploited?
What is the CVSS score of CVE-2026-85580?
How do I remediate CVE-2026-85580?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-85580
Is Your Infrastructure Affected by CVE-2026-85580?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.