Quick answers
- Is CVE-2026-42445 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-42445 being exploited in the wild.
- How severe is CVE-2026-42445?
- Low severity, with a CVSS score of 3.3, published 12 May 2026.
- Which products and versions are affected?
- M2Team NanaZip 5.0.1252.0 to before 6.0.1698.0.
- Is there a fix for CVE-2026-42445?
- A patch was published on 2026-05-12: Fixed in version 6.0.1698.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-42445 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-42445?
- Check whether you run M2Team NanaZip 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
An uncontrolled recursion vulnerability exists in the UFS/UFS2 filesystem image parser within NanaZip's 'GetAllPaths' function. The function lacks a recursion depth limit and does not track visited inodes, allowing a crafted UFS image with a deep directory tree or an inode cycle to exhaust the thread stack. On Windows, this results in a STATUS_STACK_OVERFLOW exception and a deterministic process crash. The vulnerability is triggered at archive open time due to file associations. It has been remediated in version 6.0.1698.0 by implementing proper recursion safeguards.
Affected products
- M2Team NanaZip 5.0.1252.0 to before 6.0.1698.0
Timeline
- 2025-02-01: other: Vulnerability introduced in version 5.0.1250.0
- 2026-04-27: advisory: GitHub Security Advisory published
- 2026-05-12: disclosed: CVE-2026-42445 published
- 2026-05-12: patched: Fixed in version 6.0.1698.0