Quick answers
- Is CVE-2026-42269 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-42269 being exploited in the wild.
- How severe is CVE-2026-42269?
- High severity, with a CVSS score of 8.1, published 16 October 2026.
- Which products and versions are affected?
- Countly-Server before 24.05.50 and 25.03.44.
- Is there a fix for CVE-2026-42269?
- Yes: fixed in 24.05.50, 25.03.44. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-42269 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-42269?
- Check whether you run Countly-Server 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: 24.05.50, 25.03.44
Technical details
The data-migration deletion route in plugins/data_migration/api/api.js passes an unsanitized user-controlled exportid parameter to a path concatenation operation without validation, allowing traversal outside the intended import directory. An attacker with authentication and migration permissions can craft a malicious exportid containing path traversal sequences (e.g., ../) to target and recursively delete files or directory trees via the clean_up_data function.
Affected products
- Countly Server before 24.05.50 and 25.03.44
Timeline
- 2026-10-16: disclosed