Quick answers
- Is CVE-2026-119300 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119300 being exploited in the wild.
- How severe is CVE-2026-119300?
- Medium severity, with a CVSS score of 6.5, published 30 October 2026.
- Which products and versions are affected?
- WeKan prior to 11.11.
- Is there a fix for CVE-2026-119300?
- Yes: fixed in 11.11. Until then: Escape user-controlled search input before passing to RegExp() and implement rate-limiting on search endpoints to throttle excessive queries. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-119300 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-119300?
- Check whether you run WeKan at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 11.11
Escape user-controlled search input before passing to RegExp() and implement rate-limiting on search endpoints to throttle excessive queries.
Technical details
The user-search publication and searchUsers method pass unsanitized, user-controlled search input directly to RegExp() without escaping regex metacharacters. A logged-in attacker can submit catastrophic-backtracking patterns that cause PCRE2 regex evaluation on MongoDB to consume database CPU. The searchUsers method additionally requires board membership or site-admin status. Deployments using FerretDB v1 with RE2 regex engine are not practically affected by catastrophic backtracking.
Affected products
- Wekan Wekan prior to 11.11
Timeline
- 2026-10-30: disclosed
- 2026-08-25: patched: fixed in v11.11