CVE-2026-68561

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (43rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-62703 (ENISA EUVD)Source: ENISA EUVD

8.8EG
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.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Wekan is open source kanban built with Meteor. Prior to 9.89, the second Boards.allow({ update }) rule in server/permissions/boards.js called canUpdateBoardSort in server/lib/utils.js, which authorized any board member whenever fieldNames included sort. Because Meteor combines allow rules with OR semantics and applies the complete modifier, a comment-only or read-only member could send one Boards.update with $set values for sort, members, permission, and title, make themselves the sole board administrator, expose a private board, and evict the legitimate owner; the last-admin deny rule inspected only $pull and did not block a wholesale $set of members. Version 9.89 requires sort to be the only modified field and rejects $set member arrays that remove the last active administrator. This issue is fixed in version 9.89.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
56
EG Risk 56/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)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 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.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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
43rd
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.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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, Track* at medium and Attend at high mission impact.

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 no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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 19, 2026

Last Modified

October 26, 2026

Advisory Details (3)

Auto-updated Aug 19, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

v9.89

Patch available: wekan/wekan v9.89

https://github.com/wekan/wekan/releases/tag/v9.89
GitHub commit

commit dc135f6e7d59 (wekan/wekan)

Fix landed in wekan/wekan commit dc135f6e7d59 — awaiting tagged release

https://github.com/wekan/wekan/commit/dc135f6e7d59f9f56065cd5df83b1f123ea120bb
GitHub advisoryMentions a patch (unverified)

Wekan: a low-privilege board member escalates to board admin and takes over a private board via the `sort` collection-allow rule · Advisory · wekan/wekan · GitHub

https://github.com/wekan/wekan/security/advisories/GHSA-xm8x-c8wg-jhmf

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 44× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 100 of 121 refreshes 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 21 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-68561?
CVE-2026-68561 is a high-severity vulnerability; its CVE record was published on August 19, 2026. Wekan is open source kanban built with Meteor. Prior to 9.89, the second Boards.allow({ update }) rule in server/permissions/boards.js called canUpdateBoardSort in server/lib/utils.js, which authorized any board member whenever fieldNames included sort. Because Meteor combines allow rules with OR…
When was the CVE record for CVE-2026-68561 published?
The CVE record for CVE-2026-68561 was published on August 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-68561 actively exploited?
CVE-2026-68561 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-68561?
CVE-2026-68561 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-68561?
A fix for CVE-2026-68561 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-68561

Explore →

Is Your Infrastructure Affected by CVE-2026-68561?

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

Book a Demo →Browse All CVEs