dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2026-47222

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 out-of-bounds read exists in the Android Verified Boot (AVB) vbmeta image parser in NanaZip (via the upstream 7-Zip AvbHandler). An unsigned integer underflow in a bounds check allows an attacker-controlled value_num_bytes field to pass validation, causing AddNameToString to read up to ~4 GiB past the end of a 64 KiB heap buffer. This causes a deterministic crash (denial of service) when opening a crafted .avb or .img file. This issue has been patched in stable version 6.0.1698.0 and preview version 6.5.1742.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A heap out-of-bounds read vulnerability exists in NanaZip versions 3.0.1000.0 through before 6.0.1698.0 in the AVB vbmeta image parser. An unsigned integer underflow in a bounds check allows a crafted value_num_bytes field in .avb or .img files to bypass validation, causing AddNameToString to read up to ~4 GiB past the end of a 64 KiB heap buffer, resulting in deterministic denial of service.

MitigationUpdate NanaZip to version 6.0.1698.0 (stable) or 6.5.1742.0 (preview) to patch the integer underflow vulnerability in the AVB parser.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify NanaZip is installed
    Check for NanaZip in installed programs list (Windows Settings > Apps & features, or via PowerShell: Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*NanaZip*'})
    Affected if NanaZip is present on the system
  2. Determine installed NanaZip version
    Right-click a NanaZip file in Explorer, select Properties, and check the Version tab; or use PowerShell: (Get-Item 'C:\Program Files\NanaZip\NanaZip.exe').VersionInfo.FileVersion
    Affected if Version is 3.0.1000.0 or higher but lower than 6.0.1698.0
  3. Check for recent AVB file processing activity
    Review recent file history or logs for opening .avb or .img files using NanaZip (NanaZip stores recent files; check File menu > Recent)
    Affected if User has recently opened .avb or .img files in NanaZip
  4. Confirm AVB vbmeta parser is accessible
    Attempt to open any .avb or .img file in NanaZip to verify the AVB parsing functionality is present and functional
    Affected if The AVB parser feature exists and can process .avb or .img files

User is affected if NanaZip version is between 3.0.1000.0 and 6.0.1698.0 (exclusive) and they open or have opened a crafted .avb or .img file using the built-in AVB vbmeta parser.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update NanaZip to version 6.0.1698.0 (stable) or 6.5.1742.0 (preview) to patch the integer underflow vulnerability in the AVB parser.

Recommended fix High confidence

NanaZip version 6.0.1698.0 (stable) or 6.5.1742.0 (preview)

  1. 1. Check current NanaZip version by opening NanaZip and navigating to Help > About NanaZip
  2. 2. Navigate to the official NanaZip GitHub releases page at https://github.com/M2Team/NanaZip/releases
  3. 3. Download the installer for version 6.0.1698.0 (stable) or newer (e.g., 6.5.1742.0 preview)
  4. 4. Verify the SHA-256 checksum of the downloaded installer matches the checksum listed in the release notes
  5. 5. Close NanaZip if currently running
  6. 6. Uninstall the current version of NanaZip via Windows Settings > Apps > Installed apps
  7. 7. Run the downloaded installer and follow the prompts to install the fixed version
  8. 8. Verify the installed version by checking Help > About NanaZip shows 6.0.1698.0 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47222 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47222 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data