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

CVE-2026-47223

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). A 32-bit unsigned integer overflow in the bounds check pos + ht.salt_len > descSize allows an attacker-controlled salt_len field to bypass validation, causing CByteBuffer::CopyFrom to memcpy up to ~4 GiB past the end of a 64. 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

NanaZip versions 3.0.1000.0 through 6.0.1698.0 contain a heap out-of-bounds read vulnerability in the Android Verified Boot (AVB) vbmeta image parser. A 32-bit unsigned integer overflow in the bounds check `pos + ht.salt_len > descSize` allows an attacker-controlled salt_len field to bypass validation, causing CByteBuffer::CopyFrom to memcpy up to ~4 GiB past the end of a 64-byte buffer.

MitigationUpgrade NanaZip to version 6.0.1698.0 (stable) or 6.5.1742.0 (preview) to patch the integer overflow in the AVB vbmeta parser bounds validation.

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 installation and version
    Check the installed NanaZip version. On Windows, look in Programs and Features, or right-click the NanaZip executable and view Properties > Details > File version. The version format is X.Y.ZZZZ.WWWW.
    Affected if The installed version falls within 3.0.1000.0 through 6.0.1698.0 (inclusive).
  2. Identify AVB vbmeta file processing activity
    Review recent file operations in NanaZip. The vulnerability triggers when opening or extracting Android Verified Boot (AVB) vbmeta image files, typically with .vbmeta, .img, or similar extensions used in Android system images.
    Affected if NanaZip has been used to open, extract, or browse AVB vbmeta image files.
  3. Check for suspicious vbmeta image files
    Examine any vbmeta or Android boot image files that have been opened with NanaZip. These are typically found in Android firmware dumps, custom ROM packages, or system image backups.
    Affected if Any vbmeta image files from untrusted sources have been processed with NanaZip.

A user is affected if NanaZip version 3.0.1000.0 through 6.0.1698.0 is installed and has been used to open or extract AVB vbmeta image files.

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

Upgrade NanaZip to version 6.0.1698.0 (stable) or 6.5.1742.0 (preview) to patch the integer overflow in the AVB vbmeta parser bounds validation.

Recommended fix High confidence

6.0.1698.0 (stable) or 6.5.1742.0 (preview)

  1. Check current NanaZip version by opening the application and navigating to Help > About, or checking the executable properties
  2. Download NanaZip version 6.0.1698.0 (stable) or later from the official GitHub repository (github.com/M2Team/NanaZip)
  3. Verify the downloaded installer matches the expected SHA256 hash from the release page
  4. Run the installer and follow the on-screen prompts to upgrade
  5. After installation, verify the new version by checking Help > About to confirm version 6.0.1698.0 or later is installed

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47223 — 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-47223 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