On this page

Atomicorp WAF Research Note: CVE-2026-68899

Wekan: File Upload MIME Type Validation Bypass — Stored XSS via Missing System Binary Fallback

CVE Details

Status: Attack Blocked by Atomicorp
  • Already protected by existing Atomicorp WAF rules
  • Protection status: Understanding Atomicorp WAF Protection Status
  • CVE: CVE-2026-68899
  • Name: Wekan: File Upload MIME Type Validation Bypass — Stored XSS via Missing System Binary Fallback
  • Severity: High
  • CVSS: 8.7 (v3.1) (High)
  • CVSS version: 3.1
  • CVSS source: GitHub_M CNA
  • CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
    • Attack vector: Network
    • Attack complexity: Low
    • Privileges required: Low
    • User interaction: Required
    • Scope: Changed
    • Confidentiality impact: High
    • Integrity impact: High
    • Availability impact: None
  • CWE: CWE-434 — Unrestricted Upload of File with Dangerous Type
  • Related CAPEC attack patterns (via MITRE CWE relationships): CAPEC-1
  • Vendor: wekan
  • Vulnerable product: wekan
  • CVE published: 2026-08-19
  • CVE last modified: 2026-09-09
  • EPSS: 0.0040; 33.9th percentile (FIRST )
  • Latest Update: 2026-09-06
  • Selected Rule IDs observed: 333140 , 333141 , 340095 , 340147 , 340148 , 341256 , 342259 , 346755 , 350147 , 350148
  • Matching rules: 10; rules with blocking actions: 10
  • Would-block Rule IDs: 333140 , 333141 , 340095 , 340147 , 340148 , 341256 , 342259 , 346755 , 350147 , 350148
  • Request surfaces inspected: JSON request data, Request URI, Request argument names, Request arguments, Request cookies, Request filename, Request headers, SOAP request data, XML request data

Vulnerability Description

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.

  1. Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (333140 , 333141 , 340095 , 340147 , 340148 , 341256 , 342259 , 346755 , 350147 , 350148 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.

  2. Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.

    • Affected versions: wekan version < 9.90.
    • No specific CNA/vendor solution or workaround is included in the current CVE Record . Review the vendor’s security advisories and supported-release guidance before making changes.

  3. Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.

Research Notes

Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.

Public Vulnerability References

Test or Research Source

  • Source: Atomicorp AI Research Framework
  • Tags: cve, derived, waf-probe, xss

Research Note Context

This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.

Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.

Learn More

Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.

Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:

  • Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
  • Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
  • Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
  • Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
  • Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.

For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ .