Is CVE-2026-47224 exploited in the wild?

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

How severe is CVE-2026-47224?

Medium severity, with a CVSS score of 4.3, published 12 June 2026.

Which products and versions are affected?

M2Team NanaZip 3.0.1000.0 to before 6.0.1698.0.

Is there a fix for CVE-2026-47224?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-47224 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-47224?

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-47224: M2Team NanaZip heap buffer overflow in LVM2 metadata parser

CVE-2026-47224 · Severity: medium · CVSS 4.3 · Published 2026-06-12

NanaZip is a file archiving utility for Windows based on the 7-Zip project. A security flaw in how it handles LVM disk image files could allow an attacker to crash the application or potentially leak small amounts of information if a user is tricked into opening a specially crafted file. This occurs because the software fails to properly verify the size of certain data before reading it, which can lead to a system crash or service disruption.

Technologies: M2Team NanaZip. Vendors: M2Team.

Quick answers

Is CVE-2026-47224 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-47224 being exploited in the wild.
How severe is CVE-2026-47224?: Medium severity, with a CVSS score of 4.3, published 12 June 2026.
Which products and versions are affected?: M2Team NanaZip 3.0.1000.0 to before 6.0.1698.0.
Is there a fix for CVE-2026-47224?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-47224 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-47224?: 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 heap buffer-overflow read exists in the LVM2 physical-volume metadata parser within NanaZip's LvmHandler (inherited from upstream 7-Zip but specifically enabled in NanaZip). The vulnerability is rooted in the CHandler::Open2 function in LvmHandler.cpp, where the code allocates a buffer based on an attacker-controlled size field but performs a CRC-32 check using a hardcoded length of 508 bytes. If the allocated size is less than 512 bytes, the CRC calculation reads past the end of the heap allocation. While 7-Zip contains the vulnerable code, it is not affected in its default builds because the LVM handler is disabled; NanaZip is vulnerable because it explicitly enables this handler. Attackers can trigger this by providing a malformed .lvm file, leading to a denial-of-service (crash) or a side-channel information leak via the CRC matching result.

Affected products

M2Team NanaZip 3.0.1000.0 to before 6.0.1698.0

Timeline

2026-05-18: advisory: GitHub Security Advisory published
2026-06-12: disclosed: NVD publication date

References

https://github.com/M2Team/NanaZip/security/advisories/GHSA-qcgf-c2vp-fwjr

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