dbcve.org
NanazipApplication · M2team

CVE-2026-42443

MEDIUM · 5.5 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 6.0.1698.0 or later.
See remediation →
58/100
Remediation priority · Elevated
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 an open source file archive. From 5.0.1252.0 to before 6.0.1698.0, an integer divide-by-zero exists in the UFS/UFS2 filesystem image parser in NanaZip. The vulnerability is triggered when opening a crafted UFS image where the superblock field fs_ipg (inodes per cylinder group) is set to zero. The parser uses this attacker-controlled value as a divisor without validation, causing an immediate hardware trap and process crash. This vulnerability is fixed in 6.0.1698.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 5.0.1252.0 through 6.0.1697.0 contain an integer divide-by-zero vulnerability in the UFS/UFS2 filesystem image parser. When parsing a crafted UFS image with the superblock field fs_ipg (inodes per cylinder group) set to zero, the parser uses this attacker-controlled value as a divisor without validation, causing a hardware trap and process crash.

MitigationUpgrade to NanaZip version 6.0.1698.0 or later. Avoid opening untrusted or unknown UFS/UFS2 filesystem images until the update is applied.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NanazipApplication
Affected:>= 5.0.1252.0, < 6.0.1698.0

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

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. Identify NanaZip installation
    Check for NanaZip in the list of installed programs via Windows Settings > Apps & features, or locate the executable (NanaZip.exe) in Program Files or a custom install directory.
    Affected if NanaZip is present on the system
  2. Determine installed NanaZip version
    Right-click NanaZip.exe, select Properties, and check the File version on the Details tab. Alternatively, run the executable with the --version flag if supported, or view the version in the Windows Apps & features list.
    Affected if The version is 5.0.1252.0 or higher but lower than 6.0.1698.0
  3. Verify access to UFS/UFS2 image parsing
    Launch NanaZip and check whether the application can open or mount UFS or UFS2 filesystem image files. Look for support for .ufs, .ufs2, or similar filesystem image formats in the Open dialog or supported formats list.
    Affected if NanaZip is installed in the affected version range and can open UFS/UFS2 images

A user is affected if NanaZip version 5.0.1252.0 through 6.0.1697.0 is installed and the application can be used to open UFS/UFS2 filesystem images containing a crafted superblock with fs_ipg set to zero.

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
Upgrade available Upgrade to 6.0.1698.0 or later
Fixed in 6.0.1698.0
Interim mitigation

Upgrade to NanaZip version 6.0.1698.0 or later. Avoid opening untrusted or unknown UFS/UFS2 filesystem images until the update is applied.

Recommended fix High confidence

6.0.1698.0

  1. 1. Check the currently installed NanaZip version by opening NanaZip and navigating to Help > About, or checking the application properties.
  2. 2. If the installed version is >= 5.0.1252.0 and < 6.0.1698.0, the system is vulnerable.
  3. 3. Download NanaZip version 6.0.1698.0 (or the latest version >= 6.0.1698.0) from the official GitHub releases page at github.com/M2Team/NanaZip or the Microsoft Store.
  4. 4. Install the downloaded version, overwriting the existing installation.
  5. 5. After installation, verify the new version by checking Help > About to confirm version 6.0.1698.0 or higher is installed.
  6. 6. As a general precaution, avoid opening untrusted UFS/UFS2 filesystem images from unknown sources until the upgrade is applied.

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

Fix this in Nanazip Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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