Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconCraft malicious .NET single-file bundle with oversized Size field
-
DeliveryDeliver crafted file to target via email or web
-
ExploitVictim opens file with NanaZip
-
InstallDotNetSingleFile codec reads unvalidated Size field
-
C2Heap allocation fails, std::bad_alloc or std::length_error thrown
-
ExecuteUncaught exception escapes COM STDMETHODCALLTYPE boundary
-
ImpactNanaZip process crashes
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A10:2025 - Mishandling of Exceptional Conditions
ASVS 5.0
V16 - Security Logging and Error Handling Exception handling completeness
|
| Exploitation Conditions | Exploitation requires: (1) the victim has NanaZip prior to 6.5.1749.0 installed on Windows; (2) the victim opens a crafted .NET single-file bundle (a specific archive format) using NanaZip, providing the DotNetSingleFile codec code path; (3) passive user interaction (UI:P) - the victim must initiate the file open action. Exploitation is limited to denial of service (process crash) - no code execution, privilege escalation, or data exfiltration is possible via this path. The attack does not succeed against other archive formats or other archiver tools. No network-facing surface is involved; the bundle must be present on the local filesystem for NanaZip to process it. |
| Impact | The CVSS 4.0 score of 2.4 (AV:L/AC:L/AT:N/PR:L/UI:P/VA:L) accurately reflects the constrained real-world impact. The attack vector is local - exploitation requires the victim to open a specially crafted .NET single-file bundle using NanaZip, representing meaningful user-interaction friction. The impact is strictly limited to availability (process crash) with no confidentiality or integrity consequence. No EPSS data was provided in source intelligence, and the vulnerability is not listed in CISA KEV, indicating no confirmed active exploitation. No publicly available POC code was identified. The vulnerability is straightforward in concept but requires file delivery and user action, making mass automated exploitation implausible. This is a low-priority remediation item for most organizations - highest concern applies to developer or security-research workflows where untrusted .NET single-file bundles may be routinely handled via NanaZip. SSVC assessment: exploitation status is none confirmed, technical impact is partial (DoS only), not automatable due to required UI. |
| Exploit ScenarioDerived | An attacker crafts a .NET single-file bundle with a bundle entry Size field set to a value far exceeding available memory or std::vector's max_size, then delivers it to a target via email attachment, download link, or shared drive. When the victim opens the file in a vulnerable NanaZip version, the DotNetSingleFile codec attempts to allocate the attacker-specified buffer, a C++ exception propagates across the COM boundary, and NanaZip crashes. The crash is repeatable with the same file but offers no further exploitation primitive beyond process termination. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 10, 2026
Process crash via uncaught C++ exception in NanaZip's .NET single-file bundle handler affects all versions prior to 6.5.1749.0 on Windows. The extraction buffer is sized from the bundle entry's Size field, which is validated only for sign - not against the actual file content - allowing a crafted archive to trigger an attacker-controlled allocation whose resulting std::bad_alloc or std::length_error propagates across the COM STDMETHODCALLTYPE ABI boundary and terminates the NanaZip process. Impact is limited to denial of service; no public exploit has been identified at time of analysis, and the vendor has released a fix in version 6.5.1749.0.
RemediationAI
Upgrade NanaZip to version 6.5.1749.0 or later, which contains the vendor-released patch (https://github.com/M2Team/NanaZip/releases/tag/6.5.1749.0; fix commit https://github.com/M2Team/NanaZip/commit/ad62e3b4970b9f01e924c99094d6fed7a42f849a). Organizations unable to upgrade immediately should avoid opening .NET single-file bundles from untrusted sources with NanaZip and instead use an alternative archiver for such files; this eliminates exposure entirely since the flaw is scoped to NanaZip's DotNetSingleFile codec path. No additional workarounds are documented in the advisory.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
NanaZip (CPE: cpe:2.3:a:m2team:nanazip:*:*:*:*:*:*:*:*) is a 7-Zip derivative targeting the modern Windows shell, implemented partially in C++ with COM-based codec interfaces. The affected component, NanaZip.Codecs.Archive.DotNetSingleFile.cpp, processes .NET single-file application bundles by reading a bundle entry metadata field named Size to pre-allocate an extraction buffer. The root cause is CWE-248 (Uncaught Exception): C++ exceptions (std::bad_alloc from failed heap allocation, or std::length_error from oversized container construction) are thrown inside a function declared STDMETHODCALLTYPE - a COM calling convention that requires exception-free returns. Because the Size field is not validated against the actual embedded file's real byte length, an attacker can encode an arbitrarily large value, forcing an allocation that fails and throws an exception that crosses the COM ABI boundary, which is undefined behavior in practice on Windows MSVC and results in process termination.
Know when Nanazip gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
Attacker needs no privileges to craft the file; local vector and required user interaction (opening the file) limit reach; impact is availability only.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
1DescriptionCVE.org
NanaZip is the 7-Zip derivative intended for the modern Windows experience. Prior to 6.5.1749.0, NanaZip's .NET single-file bundle handler in NanaZip.Codecs.Archive.DotNetSingleFile.cpp sizes its extraction buffer from the bundle entry Size field, which is only checked for sign and is not validated against the real file size. A crafted bundle can cause an attacker-chosen allocation inside Extract, where std::bad_alloc or std::length_error can escape across the COM STDMETHODCALLTYPE boundary and crash the process. This issue is fixed in version 6.5.1749.0.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Nanazip versions up to 6.0.1630.0 is affected by loop with unreachable exit condition (infinite loop) (CVSS 7.5).
NanaZip versions 5.0.1252.0 through 6.0.1629.0 contain an out-of-bounds heap read in the .NET Single File bundle parser
NanaZip versions 5.0.1252.0 through 6.5.1637.0 contain an out-of-bounds memory access flaw in the UFS file parser that c
Out-of-bounds memory read in NanaZip versions 5.0.1252.0 through 6.0.1637.x allows local authenticated attackers to disc
NanaZip versions 5.0.1252.0 through 6.0.1629.0 are vulnerable to denial of service through malformed ROMFS archives that
NanaZip versions 5.0.1252.0 through 6.5.1637.x contain an integer underflow in the .NET Single File Application parser t
Heap out-of-bounds read in NanaZip's SquashFS LZ4 decompression handler exposes adjacent heap memory contents when a use
A one-byte heap out-of-bounds null write (CWE-787) in NanaZip's UFS/UFS2 filesystem image parser allows a crafted .ufs,
Opening a crafted ZealFS v1 filesystem image in NanaZip builds from 5.0.1252.0 up to (but not including) 6.0.1698.0 trig
Stack exhaustion in NanaZip's UFS/UFS2 filesystem image parser crashes the application when a user opens a specially cra
Memory exhaustion in NanaZip's littlefs filesystem image parser (versions 5.0.1252.0 through before 6.0.1698.0) allows a
Integer divide-by-zero in NanaZip's UFS/UFS2 filesystem image parser crashes the application when a user opens a special
EUVD-2026-42956
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB
GitHub
VulDB