SiYuan versions before 3.7.4 contain an unthrottled brute-force vulnerability in the Publish Service Basic Auth implementation (PublishServiceTransport.RoundTrip() in kernel/server/proxy/publish.go). The Publish Service runs on a separate, unauthenticated-by-default listener (default TCP port 6808) and gates named publish-viewer accounts (Conf.Publish.Auth.Accounts) with Basic Auth that has no rate limiting, per-account lockout, or backoff. Unauthenticated remote attackers can submit unlimited password guesses against named accounts to gain access to published notes/notebooks.
CVE-2026-74868
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-17. 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
- 49(Track)EG Risk 49/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 computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 31%
- KEV
- Not listed
Published
August 17, 2026
Last Modified
August 17, 2026
Advisory Details (2)
Auto-updated Aug 17, 2026SiYuan before 3.7.4 Brute-Force Authentication via Publish Service | Advisories | VulnCheck
https://www.vulncheck.com/advisories/siyuan-before-brute-force-authentication-via-publish-serviceUnthrottled brute-force of Publish Service Basic Auth accounts in `PublishServiceTransport.RoundTrip()`, allowing unlimited automated guessing of named publish-viewer passwords on a separate, unauthenticated-by-default port · Advisory · siyuan-note/siyuan · GitHub
https://github.com/siyuan-note/siyuan/security/advisories/GHSA-phg7-xcr4-q5wgVendor Advisories for CVE-2026-74868(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 21× in last 7d / 21× 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 08:18 UTCEG score recompute
- 2026-08-21 08:18 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 19:38 UTCGHSA enrichment
- 2026-08-20 06:59 UTCGHSA enrichment
- 2026-08-19 18:20 UTCEG score recompute
- 2026-08-19 18:20 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 05:39 UTCGHSA enrichment
- 2026-08-18 16:59 UTCEG score recompute
- 2026-08-18 16:59 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 04:01 UTCGHSA enrichment
- 2026-08-17 15:21 UTCEG score recompute
- 2026-08-17 15:21 UTCGHSA enrichment
- 2026-08-17 14:44 UTCEG score recompute
- 2026-08-17 14:44 UTCGHSA enrichment
- 2026-08-17 11:42 UTCEG score recompute
- 2026-08-17 11:13 UTCEG score recompute
- 2026-08-17 11:12 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-307
Frequently asked(5)
What is CVE-2026-74868?
When was CVE-2026-74868 disclosed?
Is CVE-2026-74868 actively exploited?
What is the CVSS score of CVE-2026-74868?
How do I remediate CVE-2026-74868?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-74868
Is Your Infrastructure Affected by CVE-2026-74868?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.