SiYuan before v3.7.4 contains an incorrect authorization vulnerability in eight publish-mode reader-facing endpoints that filter results using the visibility list instead of the disabled list. Anonymous visitors can discover and read content from documents explicitly marked as forbidden from publishing by accessing search, backlink, asset content, saved criteria, recent documents, graph, and tag endpoints.
CVE-2026-74906
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-18. a secondary CVSS source baseline 7.5; 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
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 65(Attend)EG Risk 65/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 computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 22%
- KEV
- Not listed
Published
August 18, 2026
Last Modified
August 18, 2026
Advisory Details (2)
Auto-updated Aug 18, 2026SiYuan before v3.7.4 Incorrect Authorization via Publish Access | Advisories | VulnCheck
https://www.vulncheck.com/advisories/siyuan-before-incorrect-authorization-via-publish-accessSix publish-mode reader-facing endpoints filter results using the "invisible" list instead of the "disabled" (forbidden) list, leaking content from notebooks/documents an admin explicitly disabled from publishing (update: eight endpoints confirmed, see body) · Advisory · siyuan-note/siyuan · GitHub
https://github.com/siyuan-note/siyuan/security/advisories/GHSA-48p5-pffc-5r9pVendor Advisories for CVE-2026-74906(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 18× in last 7d / 18× 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-21 03:58 UTCEG score recompute
- 2026-08-21 03:57 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 15:46 UTCGHSA enrichment
- 2026-08-20 03:32 UTCEG score recompute
- 2026-08-20 03:32 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 15:19 UTCGHSA enrichment
- 2026-08-19 02:59 UTCEG score recompute
- 2026-08-19 02:59 UTCGHSA enrichment
- 2026-08-18 14:47 UTCEG score recompute
- 2026-08-18 14:47 UTCGHSA enrichment
- 2026-08-18 14:08 UTCEG score recompute
- 2026-08-18 14:07 UTCGHSA enrichment
- 2026-08-18 12:35 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-863
Frequently asked(5)
What is CVE-2026-74906?
When was CVE-2026-74906 disclosed?
Is CVE-2026-74906 actively exploited?
What is the CVSS score of CVE-2026-74906?
How do I remediate CVE-2026-74906?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-74906
Is Your Infrastructure Affected by CVE-2026-74906?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.