Quick answers
- Is CVE-2026-42355 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-42355 being exploited in the wild.
- How severe is CVE-2026-42355?
- 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 6.0.1698.0.
- Is there a fix for CVE-2026-42355?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-42355 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-42355?
- 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 (CWE-674) exists in the Electron Archive (ASAR) parser of NanaZip. The root cause is located in the ASAR handler's Open method, which passes a JSON header to the nlohmann::json::parse function and a subsequent GetAllPaths recursive function, neither of which enforce depth limits. An attacker can trigger this by providing a crafted .asar file containing approximately 2,000 levels of nested JSON. This leads to a stack overflow (STATUS_STACK_OVERFLOW) on Windows, resulting in a deterministic process crash. The vulnerability is triggered during the archive opening phase before significant user interaction occurs. It has been remediated in version 6.0.1698.0 by implementing depth limiting or converting the recursive logic to an explicit work queue.
Affected products
- M2Team NanaZip 5.0.1252.0 to 6.0.1698.0
Timeline
- 2026-04-27: advisory: GitHub Security Advisory published by M2Team
- 2026-05-12: disclosed: CVE-2026-42355 published to NVD