CVE-2026-73056

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-16. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: Elevated riskExposed: 0

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

SiYuan kernel versions before 3.7.4 contain an improper restriction of excessive authentication attempts vulnerability in the CheckAuth() middleware. The middleware accepts the API token (Conf.Api.Token) via an Authorization header (Token/Bearer) or a ?token= query parameter, and neither path is protected by the application's CAPTCHA/lockout mechanism (NeedCaptcha/WrongAuthCount). As a result, an unauthenticated remote attacker can perform unlimited automated guesses of the API token, particularly when a short or weak custom token has been configured, and upon success gains full RoleAdministrator access enabling arbitrary file operations and SQL queries.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
75(Attend)
EG Risk 75/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 computed
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

August 16, 2026

Last Modified

August 17, 2026

Advisory Details (2)

Auto-updated Aug 17, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Unthrottled brute-force of `Conf.Api.Token` via header/query auth in `CheckAuth()`, allowing unlimited automated guessing of a weakened API admin token · Advisory · siyuan-note/siyuan · GitHub

https://github.com/siyuan-note/siyuan/security/advisories/GHSA-m6w6-p7pc-fpg2
generic

SiYuan kernel before 3.7.4 Unthrottled Brute-Force via API Token | Advisories | VulnCheck

https://www.vulncheck.com/advisories/siyuan-kernel-before-unthrottled-brute-force-via-api-token

Vendor Advisories for CVE-2026-73056(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 45× in last 7d / 45× 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-08-21 05:31 UTCGHSA enrichment
  2. 2026-08-21 01:39 UTCEG score recompute
  3. 2026-08-21 01:39 UTCGHSA enrichment
  4. 2026-08-20 22:56 UTCEPSS rescore
  5. 2026-08-20 21:47 UTCGHSA enrichment
  6. 2026-08-20 17:54 UTCGHSA enrichment
  7. 2026-08-20 14:02 UTCGHSA enrichment
  8. 2026-08-20 09:49 UTCGHSA enrichment
  9. 2026-08-20 05:57 UTCGHSA enrichment
  10. 2026-08-20 02:05 UTCGHSA enrichment
  11. 2026-08-19 22:13 UTCGHSA enrichment
  12. 2026-08-19 18:21 UTCEG score recompute
  13. 2026-08-19 18:21 UTCGHSA enrichment
  14. 2026-08-19 17:04 UTCEPSS rescore
  15. 2026-08-19 14:22 UTCGHSA enrichment
  16. 2026-08-19 10:28 UTCGHSA enrichment
  17. 2026-08-19 06:36 UTCGHSA enrichment
  18. 2026-08-19 02:41 UTCGHSA enrichment
  19. 2026-08-18 22:46 UTCGHSA enrichment
  20. 2026-08-18 18:49 UTCGHSA enrichment
  21. 2026-08-18 14:57 UTCEG score recompute
  22. 2026-08-18 14:56 UTCGHSA enrichment
  23. 2026-08-18 13:49 UTCEPSS rescore
  24. 2026-08-18 13:49 UTCEPSS rescore
  25. 2026-08-18 11:00 UTCGHSA enrichment
Show 20 more
  1. 2026-08-18 07:07 UTCGHSA enrichment
  2. 2026-08-18 03:13 UTCGHSA enrichment
  3. 2026-08-17 23:20 UTCGHSA enrichment
  4. 2026-08-17 19:27 UTCEG score recompute
  5. 2026-08-17 19:27 UTCGHSA enrichment
  6. 2026-08-17 18:55 UTCEG score recompute
  7. 2026-08-17 18:55 UTCGHSA enrichment
  8. 2026-08-17 17:43 UTCEG score recompute
  9. 2026-08-17 17:43 UTCGHSA enrichment
  10. 2026-08-17 13:47 UTCEPSS rescore
  11. 2026-08-17 13:47 UTCGHSA enrichment
  12. 2026-08-17 09:55 UTCGHSA enrichment
  13. 2026-08-17 06:03 UTCGHSA enrichment
  14. 2026-08-17 02:12 UTCGHSA enrichment
  15. 2026-08-16 22:20 UTCGHSA enrichment
  16. 2026-08-16 18:28 UTCEG score recompute
  17. 2026-08-16 18:28 UTCGHSA enrichment
  18. 2026-08-16 14:36 UTCEG score recompute
  19. 2026-08-16 13:27 UTCEG score recompute
  20. 2026-08-16 13:26 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-73056?
CVE-2026-73056 is a critical vulnerability published on August 16, 2026. SiYuan kernel versions before 3.7.4 contain an improper restriction of excessive authentication attempts vulnerability in the CheckAuth() middleware. The middleware accepts the API token (Conf.Api.Token) via an Authorization header (Token/Bearer) or a ?token= query parameter, and neither path is…
When was CVE-2026-73056 disclosed?
CVE-2026-73056 was first published in the National Vulnerability Database on August 16, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73056 actively exploited?
CVE-2026-73056 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 62.4% of all scored CVEs.
What is the CVSS score of CVE-2026-73056?
CVE-2026-73056 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-73056?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73056, 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-73056

Explore →

Is Your Infrastructure Affected by CVE-2026-73056?

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

Start Free Scan →Browse All CVEs