Skip to main content
VulnerabilityPublished Updated

CVE-2026-42444: M2Team NanaZip · Unthrottled Resource Allocation

Affects M2Team NanaZipSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 3.3 Low : upgrade to 6.0.1698.0 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
3.3Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 6.0.1698.0
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade NanaZip and m2team/NanaZip to 6.0.1698.0.

Affected software

ProductAffectedFixed in
M2TeamNanaZipAffected
  • >=5.0.1250.0 <6.0.1698.0
Fixed in
  • 6.0.1698.0
GitHubm2team/NanaZippkg:github/m2team/NanaZipOther threatsAffected
  • >=5.0.1252.0 <6.0.1698.0
Fixed in
  • 6.0.1698.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is fixed in NanaZip version 6.0.1698.0. Users should upgrade to this version or later to remediate the issue. No other mitigation or temporary workaround is indicated. Patch status is confirmed by the vendor's versioning information.

Description

NanaZip is an open source file archive. From 5.0.1252.0 to before 6.0.1698.0, a denial-of-service vulnerability exists in the littlefs filesystem image parser in NanaZip. The handler's Open method reads BlockCount directly from the attacker-controlled superblock without any validation against the actual file size or any upper-bound ceiling, then iterates BlockCount times, allocating a file-path entry per iteration. A crafted 44-byte littlefs image with BlockCount = 0xFFFFFFFF causes ~4 billion heap allocations, exhausting available memory. This vulnerability is fixed in 6.0.1698.0.

References

Community reviews

Loading reviews…