CVE-2026-68899

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 66% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.7Exploit: None knownExposed: 0

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

Wekan is open source kanban built with Meteor. Prior to 9.90, isFileValid() in models/fileValidation.js used the Unix file command for content-based MIME detection, but detectMimeFromFile() silently returned undefined when that binary was unavailable and the validation fell back to the attacker-controlled fileObj.type supplied through server/routes/attachmentApi.js. On deployments with WITH_API=true and no file binary, an authenticated board member could label HTML containing JavaScript as image/png, bypass the dangerous MIME check, and store active content under the Wekan origin for execution when another user opened it. Version 9.90 adds looksLikeDangerousMarkup() to inspect file bytes and force dangerous-content scanning when MIME detection is unavailable. This issue is fixed in version 9.90.

CVSS v3
8.7
EG Score
8.7(medium)
EG Risk
39(Track)
EG Risk 39/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 computed
Severity87% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
34%
KEV
Not listed

Published

August 19, 2026

Last Modified

September 9, 2026

Advisory Details (3)

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

v9.90

Patch available: wekan/wekan v9.90

https://github.com/wekan/wekan/releases/tag/v9.90
github_commit

commit f6ba472f6738 (wekan/wekan)

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

https://github.com/wekan/wekan/commit/f6ba472f6738bcd3763f133d3d9970f216df2263
github Patch Available

File Upload MIME Type Validation Bypass — Stored XSS via Missing System Binary Fallback · Advisory · wekan/wekan · GitHub

https://github.com/wekan/wekan/security/advisories/GHSA-jhph-whx8-wq6p

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 48× 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-09-21 06:28 UTCEG score recompute
  2. 2026-09-20 20:16 UTCEPSS rescore
  3. 2026-09-19 17:01 UTCEG score recompute
  4. 2026-09-19 04:49 UTCEG score recompute
  5. 2026-09-18 19:28 UTCEPSS rescore
  6. 2026-09-18 03:54 UTCEG score recompute
  7. 2026-09-16 15:08 UTCEG score recompute
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-16 05:15 UTCEPSS rescore
  10. 2026-09-15 14:45 UTCEG score recompute
  11. 2026-09-14 01:55 UTCEG score recompute
  12. 2026-09-13 01:33 UTCEG score recompute
  13. 2026-09-12 01:11 UTCEG score recompute
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-11 12:59 UTCEG score recompute
  16. 2026-09-11 09:37 UTCEPSS rescore
  17. 2026-09-10 12:18 UTCEG score recompute
  18. 2026-09-09 02:33 UTCEG score recompute
  19. 2026-09-08 22:01 UTCEPSS rescore
  20. 2026-09-07 18:48 UTCEG score recompute
  21. 2026-09-07 16:01 UTCEPSS rescore
  22. 2026-09-06 18:10 UTCEG score recompute
  23. 2026-09-06 13:47 UTCEPSS rescore
  24. 2026-09-05 17:47 UTCEG score recompute
  25. 2026-09-05 15:31 UTCEPSS rescore
Show 32 more
  1. 2026-09-04 17:25 UTCEG score recompute
  2. 2026-09-04 05:08 UTCEG score recompute
  3. 2026-09-04 05:07 UTCEPSS rescore
  4. 2026-09-02 16:06 UTCEG score recompute
  5. 2026-09-02 14:12 UTCEPSS rescore
  6. 2026-09-01 15:24 UTCEG score recompute
  7. 2026-09-01 13:54 UTCEPSS rescore
  8. 2026-09-01 04:40 UTCEPSS rescore
  9. 2026-08-31 02:37 UTCEG score recompute
  10. 2026-08-30 19:17 UTCEPSS rescore
  11. 2026-08-30 02:14 UTCEG score recompute
  12. 2026-08-30 01:22 UTCEPSS rescore
  13. 2026-08-29 01:47 UTCEG score recompute
  14. 2026-08-28 21:42 UTCEPSS rescore
  15. 2026-08-28 00:45 UTCEG score recompute
  16. 2026-08-27 00:18 UTCEG score recompute
  17. 2026-08-26 14:47 UTCEPSS rescore
  18. 2026-08-25 23:54 UTCEG score recompute
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-24 23:32 UTCEG score recompute
  21. 2026-08-24 11:21 UTCEG score recompute
  22. 2026-08-23 10:59 UTCEG score recompute
  23. 2026-08-23 00:19 UTCEPSS rescore
  24. 2026-08-22 10:37 UTCEG score recompute
  25. 2026-08-21 23:49 UTCEPSS rescore
  26. 2026-08-21 22:26 UTCEG score recompute
  27. 2026-08-21 22:00 UTCEG score recompute
  28. 2026-08-21 08:54 UTCEG score recompute
  29. 2026-08-20 22:56 UTCEPSS rescore
  30. 2026-08-19 20:21 UTCEG score recompute
  31. 2026-08-19 19:33 UTCEG score recompute
  32. 2026-08-19 19:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68899?
CVE-2026-68899 is a high vulnerability published on August 19, 2026. Wekan is open source kanban built with Meteor. Prior to 9.90, isFileValid() in models/fileValidation.js used the Unix file command for content-based MIME detection, but detectMimeFromFile() silently returned undefined when that binary was unavailable and the validation fell back to the…
When was CVE-2026-68899 disclosed?
CVE-2026-68899 was first published in the National Vulnerability Database on August 19, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68899 actively exploited?
CVE-2026-68899 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 65.6% of all scored CVEs.
What is the CVSS score of CVE-2026-68899?
CVE-2026-68899 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-68899?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68899, 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-68899

Explore →

Is Your Infrastructure Affected by CVE-2026-68899?

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