Application hang via unchecked BlockCount allocation loop
Published May 12, 2026 · Updated May 12, 2026
Resource exhaustion in M2-Team NanaZip from 5.0.1252.0 to before 6.0.1698.0 allows attackers to hang the application via a crafted littlefs image. The littlefs handler's Open method accepts the superblock BlockCount without checking the file size or applying a ceiling, then allocates one path entry per declared block. Opening the 44-byte file is required; BlockCount 0xFFFFFFFF drives about four billion heap allocations, exhausts memory, and does not enable code execution.
Summary
What happened
Resource exhaustion in M2-Team NanaZip from 5.0.1252.0 to before 6.0.1698.0 allows attackers to hang the application via a crafted littlefs image. The littlefs handler's Open method accepts the superblock BlockCount without checking the file size or applying a ceiling, then allocates one path entry per declared block. Opening the 44-byte file is required; BlockCount 0xFFFFFFFF drives about four billion heap allocations, exhausts memory, and does not enable code execution.
The record
- CVE
- CVE-2026-42444
- Published
- May 12, 2026
- Updated
- May 12, 2026
- Vendor
- M2-Team
- Product
- NanaZip
- Classifications
- CWE-770, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 12, 2026CVE publishedPublication date reported by the CVE source.
- May 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 5.0.1250.0, < 6.0.1698.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo