Quick answers
- Is CVE-2026-52890 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-52890 being exploited in the wild.
- How severe is CVE-2026-52890?
- High severity, with a CVSS score of 7.1, published 15 July 2026.
- Which products and versions are affected?
- WeKan < 9.31.
- Is there a fix for CVE-2026-52890?
- A patch was published on 2026-05-27: Fix included in release v9.31 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-52890 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-52890?
- 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.
Technical details
A path traversal vulnerability exists in Wekan's attachment handling prior to version 9.31. While the application implemented a check to prevent path traversal during file updates, it failed to apply similar logic to the initial insertion via the '/attachments/insert' DDP method. An authenticated board member can provide a crafted document containing absolute filesystem paths in the 'versions.original.path' field. Because 'FileStoreStrategyFilesystem.getReadStream()' lacks a storage-root containment check, it will stream any file accessible to the application process. Attackers can exploit this to read sensitive environment variables (like MONGO_URL) or cause a denial of service by requesting special system files like '/dev/zero', which exhausts memory during the buffering process.
Affected products
- Wekan Wekan < 9.31
Timeline
- 2026-05-27: patched: Fix included in release v9.31
- 2026-05-30: advisory: GitHub Security Advisory GHSA-g6vm-7757-pr88 published
- 2026-07-15: disclosed: CVE-2026-52890 published to NVD