CVE-2026-93921

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: secondary
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 4.3Exploit: None knownExposed: 0

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

SiYuan versions through 3.8.4 fail to enforce publish access control in the getDynamicIcon endpoint, allowing read-only token holders to access document metadata. Attackers can call the endpoint with type=8 and crafted content to read block titles, names, aliases, and hierarchical paths of restricted documents via template injection.

CVSS v3
4.3
EG Score
4.3(low)
EG Risk
24(Track)
EG Risk 24/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 computed
Severity43% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

Published

September 18, 2026

Last Modified

September 19, 2026

Advisory Details (6)

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

SiYuan through 3.8.4 Access Control Bypass via Dynamic Icon Endpoint | Advisories | VulnCheck

https://www.vulncheck.com/advisories/siyuan-through-3.8.4-access-control-bypass-via-dynamic-icon-endpoint
generic

siyuan/kernel/api/icon.go at v3.8.4 · siyuan-note/siyuan · GitHub

https://github.com/siyuan-note/siyuan/blob/v3.8.4/kernel/api/icon.go#L546-L549
generic

siyuan/kernel/model/template.go at v3.8.4 · siyuan-note/siyuan · GitHub

https://github.com/siyuan-note/siyuan/blob/v3.8.4/kernel/model/template.go#L485-L526
generic

siyuan/kernel/api/router.go at v3.8.4 · siyuan-note/siyuan · GitHub

https://github.com/siyuan-note/siyuan/blob/v3.8.4/kernel/api/router.go#L51
generic

GitHub - siyuan-note/siyuan: An open-source, privacy-first, self-hosted knowledge workspace where humans and AI agents work together 开源、隐私优先、自托管的知识工作空间，让人与智能体在此协作 · GitHub

https://github.com/siyuan-note/siyuan
github Patch Available🟡 PoC Available

Publish Access Bypass via Unchecked Dynamic Icon Templates Leaks Password-Protected, Disabled, and Encrypted Document Metadata · Advisory · siyuan-note/siyuan · GitHub

https://github.com/siyuan-note/siyuan/security/advisories/GHSA-whcx-xxqh-c838

Vendor Advisories for CVE-2026-93921(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 3× in last 7d / 3× 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-09-19 00:21 UTCEG score recompute
  2. 2026-09-18 23:23 UTCEG score recompute
  3. 2026-09-18 23:22 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2026-93921?
CVE-2026-93921 is a medium vulnerability published on September 18, 2026. SiYuan versions through 3.8.4 fail to enforce publish access control in the getDynamicIcon endpoint, allowing read-only token holders to access document metadata. Attackers can call the endpoint with type=8 and crafted content to read block titles, names, aliases, and hierarchical paths of…
When was CVE-2026-93921 disclosed?
CVE-2026-93921 was first published in the National Vulnerability Database on September 18, 2026, with the most recent update on September 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-93921?
CVE-2026-93921 has a CVSS v3 base score of 4.3 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-93921?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-93921, 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-93921

Explore →

Is Your Infrastructure Affected by CVE-2026-93921?

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

Start Free Scan →Browse All CVEs