CVE-2026-68899
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 33% of all known CVEs.
References
Related Vulnerabilities
Other CWE-434 (Unrestricted File Upload) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2017-12617 | High | 8.1 | 100% | KEV | Fix |
| CVE-2018-15961 | Critical | 9.8 | 100% | KEV | - |
| CVE-2021-31207 | Medium | 6.6 | 100% | KEV + Ransom | Fix |
| CVE-2017-12615 | High | 8.1 | 100% | KEV + Ransom | - |
| CVE-2025-31324 | Critical | 10.0 | 100% | KEV + Ransom | - |
| CVE-2024-50623 | Critical | 9.8 | 99% | KEV + Ransom | Fix |
Common questions
How do I fix CVE-2026-68899?
No published fix for CVE-2026-68899 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-68899 being actively exploited?
Not that we know of. CVE-2026-68899 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.40% is the estimated probability that it will be exploited in the next 30 days. That is higher than 33% of all scored CVEs.
How severe is CVE-2026-68899?
CVE-2026-68899 has a CVSS v3 base score of 8.7, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-68899
Markdown
[](https://tridentstack.com/cve/CVE-2026-68899)HTML
<a href="https://tridentstack.com/cve/CVE-2026-68899"><img src="https://tridentstack.com/cve/badge/CVE-2026-68899.svg" alt="CVE-2026-68899"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-21.