Is CVE-2026-55782 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-55782 being exploited in the wild.

How severe is CVE-2026-55782?

Informational severity, with a CVSS score of 2.4, published 10 July 2026.

Is there a fix for CVE-2026-55782?

A patch was published on 2026-06-16: Fixed in version 6.5.1749.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-55782 attacked?

It is attacked with local access, in a network appliance.

Am I affected by CVE-2026-55782?

Check whether you run M2Team NanaZip at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-55782: M2Team NanaZip uncontrolled memory allocation in WebAssembly handler

CVE-2026-55782 · Severity: info · CVSS 2.4 · Published 2026-07-10

NanaZip is an open-source file archiver for Windows. A vulnerability in its WebAssembly file handler allows a specially crafted, small file to trigger massive memory allocations when the file is opened or extracted. This can lead to the application crashing or the system running out of memory, potentially causing a denial of service for the user.

Technologies: M2Team NanaZip. Vendors: M2Team.

Quick answers

Is CVE-2026-55782 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-55782 being exploited in the wild.
How severe is CVE-2026-55782?: Informational severity, with a CVSS score of 2.4, published 10 July 2026.
Which products and versions are affected?: M2Team NanaZip < 6.5.1749.0.
Is there a fix for CVE-2026-55782?: A patch was published on 2026-06-16: Fixed in version 6.5.1749.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-55782 attacked?: It is attacked with local access, in a network appliance.
Am I affected by CVE-2026-55782?: Check whether you run M2Team NanaZip at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A vulnerability exists in NanaZip's WebAssembly archive handler (NanaZip.Codecs.Archive.WebAssembly.cpp) due to improper validation of ULEB128 length fields. Specifically, the 'NameSize' and 'Information.Size' fields are used to allocate std::string and std::vector buffers without being checked against the actual file size or remaining stream bytes. An attacker can provide a tiny .wasm file with a declared name length of 0xFFFFFFFF, forcing a ~4 GiB allocation during the archive listing (Open) or extraction phase. This results in a denial of service via memory exhaustion (std::bad_alloc). The issue is fixed in version 6.5.1749.0 by implementing bounds checking against the remaining bundle size.

Affected products

M2Team NanaZip < 6.5.1749.0

Timeline

2026-06-16: advisory: GitHub Security Advisory published
2026-06-16: patched: Fixed in version 6.5.1749.0
2026-07-10: disclosed: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.