NanaZip: Unbounded memory allocation (DoS) in NanaZip WebAssembly parser via attacker-controlled section/name length fields

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

• M2Team NanaZip

  • < 6.5.1749.0affected

Other highest-scoring records for the same primary product.

• CVE-2026-54616NanaZip: Heap out-of-bounds read in NanaZip SquashFS LZ4 decompressor via unchecked negative return value
  28Monitor
• CVE-2026-44215NanaZip: Heap out-of-bounds write in NanaZip UFS directory parser
  28Monitor
• CVE-2026-42446NanaZip: Stack out-of-bounds read in NanaZip ZealFS bitmap parser
  28Monitor
• CVE-2026-42445NanaZip: Uncontrolled recursion in NanaZip UFS directory traversal causes stack exhaustion
  22Monitor
• CVE-2026-42444NanaZip: Unbounded resource consumption in NanaZip littlefs parser via attacker-controlled BlockCount
  22Monitor
• CVE-2026-42443NanaZip: Integer divide-by-zero in NanaZip UFS inode offset calculation
  22Monitor

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Root cause

Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1function expand(node) {2  return node.children.map(expand);3}

1const MAX_DEPTH = 32;2function expand(node, depth = 0) {3  if (depth > MAX_DEPTH) throw new Error("too deep");4  return node.children.map((c) => expand(c, depth + 1));5}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.