Skip to main content

NanaZip EUVDEUVD-2026-42956

| CVE-2026-55780 LOW
Uncaught Exception (CWE-248)
2026-07-10 GitHub_M
2.4
CVSS 4.0 · Vendor: GitHub_M
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Craft malicious .NET single-file bundle with oversized Size field
  2. Delivery
    Deliver crafted file to target via email or web
  3. Exploit
    Victim opens file with NanaZip
  4. Install
    DotNetSingleFile codec reads unvalidated Size field
  5. C2
    Heap allocation fails, std::bad_alloc or std::length_error thrown
  6. Execute
    Uncaught exception escapes COM STDMETHODCALLTYPE boundary
  7. Impact
    NanaZip 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.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

NanaZip < 6.5.1749.0

Affected Packages

euvd nanazip fix: 6.5.1749.0

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

Vendor (GitHub_M) PRIMARY 2.4 LOW
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
vuln.today AI 3.3 LOW

Attacker needs no privileges to craft the file; local vector and required user interaction (opening the file) limit reach; impact is availability only.

3.1 AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
4.0 AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
Passive
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
None
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

1
Patch available
Jul 10, 2026 - 18:01 EUVD

DescriptionCVE.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

EPSS Score
0.1%
Top 98% exploitable
Prevalence
Low
niche Windows 7-Zip derivative, primarily power-user/developer audience
Exploit
POC
Public exploit code exists
Data Quality
8 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment Exploit-DB GitHub VulDB

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.

SignalValue
Severity LOW
CISA KEV No
Public POC Yes
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation
Poc
System Exposure· derived
Small
Automatable
No
Human Impact· derived
Low
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +12
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

CVE-2026-27114 HIGH POC
7.5 Feb 19

Nanazip versions up to 6.0.1630.0 is affected by loop with unreachable exit condition (infinite loop) (CVSS 7.5).

CVE-2026-26282 MEDIUM POC
6.6 Feb 19

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

CVE-2026-27711 MEDIUM POC
6.6 Feb 26

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

CVE-2026-27709 MEDIUM POC
6.6 Feb 26

Out-of-bounds memory read in NanaZip versions 5.0.1252.0 through 6.0.1637.x allows local authenticated attackers to disc

CVE-2026-27014 MEDIUM POC
5.5 Feb 19

NanaZip versions 5.0.1252.0 through 6.0.1629.0 are vulnerable to denial of service through malformed ROMFS archives that

CVE-2026-27710 MEDIUM POC
5.0 Feb 26

NanaZip versions 5.0.1252.0 through 6.5.1637.x contain an integer underflow in the .NET Single File Application parser t

CVE-2026-54616 HIGH
7.1 Aug 20

Heap out-of-bounds read in NanaZip's SquashFS LZ4 decompression handler exposes adjacent heap memory contents when a use

CVE-2026-44215 HIGH
7.1 May 12

A one-byte heap out-of-bounds null write (CWE-787) in NanaZip's UFS/UFS2 filesystem image parser allows a crafted .ufs,

CVE-2026-42446 HIGH
7.1 May 12

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

CVE-2026-42445 MEDIUM
5.5 May 12

Stack exhaustion in NanaZip's UFS/UFS2 filesystem image parser crashes the application when a user opens a specially cra

CVE-2026-42444 MEDIUM
5.5 May 12

Memory exhaustion in NanaZip's littlefs filesystem image parser (versions 5.0.1252.0 through before 6.0.1698.0) allows a

CVE-2026-42443 MEDIUM
5.5 May 12

Integer divide-by-zero in NanaZip's UFS/UFS2 filesystem image parser crashes the application when a user opens a special

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy