CVE-2026-68584

HIGHPre-NVD 8.68.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.6 from GitHub Security Advisory (severity: HIGH) published 2026-09-03. A secondary CVSS source baseline 8.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-52272 (ENISA EUVD) · GHSA-7j72-f6wg-cxw6 (GitHub Security Advisories) · GHSA-g64v-qqpg-v37h (GitHub Security Advisories) · GO-2026-6382 (OSV.dev)Source: ENISA EUVD

8.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.6Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

SiYuan versions before v3.7.3 contain an authentication bypass vulnerability in publish mode where content-returning endpoints getHeadingChildrenDOM, getHeading*Transaction, and getBacklinkDoc perform no password check despite protecting the primary getDoc endpoint. Anonymous attackers can retrieve full content of password-protected documents by obtaining internal block IDs from reader-accessible endpoints and calling unprotected content endpoints to bypass the password gate.

CVSS v3
8.6
EG Score
8.6HIGHmedium confidence
EG Risk
70
EG Risk 70/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity86% × 45%
Impact severity (EG Severity): CVSS 8.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
45th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.6): severity, escalated by confirmed exploitation. This CVE's 8.6 is its impact severity (EG Severity), not escalated.

EG Severity
8.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 3, 2026

Last Modified

October 23, 2026

Advisory Details (2)

Auto-updated Aug 3, 2026
Patch available. Sources: github.
Web page

SiYuan before v3.7.3 Authentication Bypass via Content Endpoints | Advisories | VulnCheck

https://www.vulncheck.com/advisories/siyuan-before-authentication-bypass-via-content-endpoints
GitHub advisoryMentions a patch (unverified)

Anonymous publish-password authentication bypass via getHeadingChildrenDOM / getHeading*Transaction / getBacklinkDoc (publish mode): content endpoints perform no password check, chained to full disclosure of password-protected documents · Advisory · siyuan-note/siyuan · GitHub

https://github.com/siyuan-note/siyuan/security/advisories/GHSA-7j72-f6wg-cxw6

Vendor Advisories for CVE-2026-68584(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/siyuan-note/siyuan/kernel @ 0.0.0-20260721020826-2d069dce84a2 (fixes < 0.0.0-20260721020826-2d069dce84a2)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/siyuan-note/siyuan/kernel—
  • every version up to 0.0.0-20260721020826-2d069dce84a2: fixed in 0.0.0-20260721020826-2d069dce84a2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 33× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 230 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 130 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:57 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  2. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  3. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  4. 2026-11-11 05:04 UTCEchelonGraph re-scored
  5. 2026-11-11 05:04 UTCGHSA enrichmentGHSA-7j72-f6wg-cxw6 · GitHub severity HIGH · GitHub CVSS 8.6
  6. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  7. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  8. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  9. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  10. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  11. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  12. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  13. 2026-11-04 00:32 UTCEchelonGraph re-scored
  14. 2026-11-04 00:32 UTCGHSA enrichmentGHSA-7j72-f6wg-cxw6 · GitHub severity HIGH · GitHub CVSS 8.6
  15. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  16. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  17. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  18. 2026-11-01 07:40 UTCGHSA enrichmentGHSA-7j72-f6wg-cxw6 · GitHub severity HIGH · GitHub CVSS 8.6
  19. 2026-11-01 07:40 UTCEchelonGraph re-scored
  20. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  21. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  22. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  23. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  24. 2026-10-27 21:07 UTCEchelonGraph re-scored
  25. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
Show 75 more
  1. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  2. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  3. 2026-10-25 14:09 UTCEchelonGraph re-scored
  4. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  5. 2026-10-23 21:29 UTCEchelonGraph re-scored
  6. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  7. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  8. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  9. 2026-10-20 18:38 UTCEchelonGraph re-scored
  10. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  11. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  12. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  13. 2026-10-18 03:19 UTCEchelonGraph re-scored
  14. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  15. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  17. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  18. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  19. 2026-10-13 10:03 UTCEchelonGraph re-scored
  20. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  21. 2026-10-12 15:45 UTCEchelonGraph re-scored
  22. 2026-10-11 19:30 UTCEchelonGraph re-scored
  23. 2026-10-11 16:45 UTCEchelonGraph re-scored
  24. 2026-10-11 14:06 UTCEchelonGraph re-scored
  25. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  26. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  27. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  28. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  29. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  30. 2026-10-06 23:46 UTCEchelonGraph re-scored
  31. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  32. 2026-10-05 19:48 UTCEchelonGraph re-scored
  33. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  34. 2026-10-04 23:46 UTCEchelonGraph re-scored
  35. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  36. 2026-10-04 06:19 UTCEchelonGraph re-scored
  37. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  38. 2026-10-03 02:37 UTCEchelonGraph re-scored
  39. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  40. 2026-10-02 10:21 UTCEchelonGraph re-scored
  41. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  42. 2026-10-01 02:36 UTCEchelonGraph re-scored
  43. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  44. 2026-09-29 06:42 UTCEchelonGraph re-scored
  45. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  46. 2026-09-27 18:16 UTCEchelonGraph re-scored
  47. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  48. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  49. 2026-09-25 04:47 UTCEchelonGraph re-scored
  50. 2026-09-23 22:04 UTCEchelonGraph re-scored
  51. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  52. 2026-09-22 21:26 UTCEchelonGraph re-scored
  53. 2026-09-22 05:31 UTCEchelonGraph re-scored
  54. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  55. 2026-09-20 20:56 UTCEchelonGraph re-scored
  56. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  57. 2026-09-19 17:51 UTCEchelonGraph re-scored
  58. 2026-09-19 03:45 UTCEchelonGraph re-scored
  59. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  60. 2026-09-18 01:11 UTCEchelonGraph re-scored
  61. 2026-09-17 01:15 UTCEchelonGraph re-scored
  62. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  63. 2026-09-16 05:19 UTCEchelonGraph re-scored
  64. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  65. 2026-09-15 16:57 UTCEchelonGraph re-scored
  66. 2026-09-13 22:12 UTCEchelonGraph re-scored
  67. 2026-09-12 21:34 UTCEchelonGraph re-scored
  68. 2026-09-11 20:56 UTCEchelonGraph re-scored
  69. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  70. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  71. 2026-09-10 20:18 UTCEchelonGraph re-scored
  72. 2026-09-09 06:47 UTCEchelonGraph re-scored
  73. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  74. 2026-09-07 18:56 UTCEchelonGraph re-scored
  75. 2026-09-07 18:56 UTCGHSA enrichmentGHSA-g64v-qqpg-v37h · GitHub severity CRITICAL · GitHub CVSS 8.6

Frequently asked(5)

What is CVE-2026-68584?
CVE-2026-68584 is a high-severity vulnerability; its CVE record was published on August 3, 2026. SiYuan versions before v3.7.3 contain an authentication bypass vulnerability in publish mode where content-returning endpoints getHeadingChildrenDOM, getHeading*Transaction, and getBacklinkDoc perform no password check despite protecting the primary getDoc endpoint. Anonymous attackers can retrieve…
When was CVE-2026-68584 made public?
CVE-2026-68584 was made public on July 21, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 3, 2026. EchelonGraph's copy of the record carries a last-modified date of October 23, 2026; the record at its source may have been updated since.
Is CVE-2026-68584 actively exploited?
CVE-2026-68584 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-68584?
CVE-2026-68584 has a CVSS base score of 8.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-68584?
A fix for CVE-2026-68584 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-68584 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-68584

Explore →

Is Your Infrastructure Affected by CVE-2026-68584?

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