CVE-2026-44215: GHSL-2026-124_GHSL-2026-134: Memory corruption, information disclosure, and denial of service in NanaZip - CVE-2026-54616, CVE-2026-44215, CVE-2026-47222, CVE-2026-47223, CVE-2026-42446, CVE-2026-47224, CVE-2026-42442, CVE-2026-42443, CVE-2026-42445, CVE-2026-42355, CVE-2026-42444
NanaZip contains memory-safety, parsing, and resource-exhaustion vulnerabilities that can cause memory corruption, information disclosure, or denial of service.
Other sources
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.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
NanaZipto a version that resolves this vulnerability.Fixed in 6.0.1698.0
Event History
Frequently Asked Questions
What is the severity of CVE-2026-44215?
CVE-2026-44215 is classified as a high-severity vulnerability due to the potential for heap out-of-bounds writes.
How do I fix CVE-2026-44215?
To fix CVE-2026-44215, update NanaZip to version 6.0.1698.0 or later.
What versions of NanaZip are affected by CVE-2026-44215?
NanaZip versions from 5.0.1252.0 to before 6.0.1698.0 are affected by CVE-2026-44215.
What type of vulnerability is CVE-2026-44215?
CVE-2026-44215 is a heap out-of-bounds write vulnerability found in the UFS directory parser of NanaZip.
What can occur if CVE-2026-44215 is exploited?
Exploitation of CVE-2026-44215 could lead to severe data corruption or application crashes when processing specially crafted UFS filesystem images.