CVE-2026-44215: M2Team NanaZip · Out-of-bounds Write
Affects M2Team NanaZipSource CVE Database V5
Not known to be exploited · CVSS 4.4 Medium : upgrade to 6.0.1698.0 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% 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:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 12 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 30 Oct 2026.
What to do
Upgrade NanaZip and m2team/NanaZip to 6.0.1698.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| M2TeamNanaZip | Affected
| Fixed in
|
GitHubm2team/NanaZippkg:github/m2team/NanaZipOther threats | Affected
| Fixed in
|
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 official remediation or temporary fixes are 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 one-byte heap out-of-bounds null write exists in the UFS/UFS2 filesystem image parser in NanaZip. The vulnerability is triggered when opening a crafted UFS filesystem image. The attacker controls the byte offset of the write within a ~254-byte window past the heap allocation boundary. This vulnerability is fixed in 6.0.1698.0.