# CVE-2026-47224: NanaZip: Heap buffer-overflow read in NanaZip LVM metadata CRC check

> Attackers can cause a heap buffer overflow read in NanaZip by tricking users into opening a crafted LVM disk image, potentially leading to crashes or information disclosure.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Jun 2026
- **Updated:** 12 Jun 2026
- **Also known as:** GHSA-qcgf-c2vp-fwjr

## What is CVE-2026-47224?

CVE-2026-47224 is a medium-severity memory corruption vulnerability in M2Team NanaZip, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

NanaZip is the 7-Zip derivative intended for the modern Windows experience. From version 3.0.1000.0 to before version 6.0.1698.0, a heap buffer-overflow read exists in the LVM2 physical-volume metadata parser in NanaZip (via the upstream 7-Zip LvmHandler). The vulnerability is triggered when opening a crafted LVM disk image. This issue has been patched in stable version 6.0.1698.0 and preview version 6.5.1742.0.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-47224?


## How do I fix CVE-2026-47224?

No fix has been published for CVE-2026-47224 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-47224 being exploited?

There is no known exploitation of CVE-2026-47224 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47224 and fix it if it is affected.

What it is: CVE-2026-47224 is a medium-severity memory corruption vulnerability in M2Team NanaZip, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-47224 in the wild and no public exploit code.

Affected product: M2Team NanaZip. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47224/ (Markdown: https://insights.sbomify.com/CVE-2026-47224/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47224
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47224
- OSV: https://osv.dev/vulnerability/CVE-2026-47224

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47224/
Summaries are generated and may contain mistakes; the official description above is the record.