SiYuan before v3.7.4 contains an insufficient access control vulnerability in the /api/lute/spinBlockDOM endpoint, which is guarded only by CheckAuth middleware instead of CheckAdminRole like its sibling endpoint. Authenticated users with RoleEditor or RoleReader roles can invoke the endpoint to transform arbitrary DOM input, and large payloads cause endpoint starvation through per-path mutex serialization.
CVE-2026-74903
Score 4.3 from GitHub Security Advisory published 2026-08-18. a secondary CVSS source baseline 4.3; 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
- 4.3
- EG Score
- 4.3(high)
- EG Risk
- 35(Track)EG Risk 35/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 computedSeverity43% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 11%
- KEV
- Not listed
Published
August 18, 2026
Last Modified
August 18, 2026
Advisory Details (2)
Auto-updated Aug 18, 2026SiYuan before v3.7.4 Insufficient Access Control via spinBlockDOM | Advisories | VulnCheck
https://www.vulncheck.com/advisories/siyuan-before-insufficient-access-control-via-spinblockdom/api/lute/spinBlockDOM Accessible to All Authenticated Roles Without Admin Gate or Input Size Limit · Advisory · siyuan-note/siyuan · GitHub
https://github.com/siyuan-note/siyuan/security/advisories/GHSA-3j8q-5c8c-grwmVendor Advisories for CVE-2026-74903(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 13× in last 7d / 13× 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 22:56 UTCEPSS rescore
- 2026-08-20 19:56 UTCGHSA enrichment
- 2026-08-19 18:16 UTCEG score recompute
- 2026-08-19 18:16 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 15:23 UTCEG score recompute
- 2026-08-18 15:22 UTCGHSA enrichment
- 2026-08-18 15:15 UTCEG score recompute
- 2026-08-18 15:15 UTCGHSA enrichment
- 2026-08-18 12:36 UTCEG score recompute
- 2026-08-18 12:35 UTCGHSA enrichment
- 2026-08-18 11:29 UTCEG score recompute
- 2026-08-18 11:29 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-400
Frequently asked(5)
What is CVE-2026-74903?
When was CVE-2026-74903 disclosed?
Is CVE-2026-74903 actively exploited?
What is the CVSS score of CVE-2026-74903?
How do I remediate CVE-2026-74903?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-74903
Is Your Infrastructure Affected by CVE-2026-74903?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.