dbcve.org
NanazipApplication · M2team

CVE-2026-42442

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, a null-pointer dereference exists in the UFS/UFS2 filesystem image parser in NanaZip. The vulnerability is triggered when opening a crafted UFS image where the root inode (inode 2) is set to IFLNK (symlink) instead of IFDIR (directory). The parser unconditionally treats the root inode as a directory without checking its type, and when the symlink has an embedded target (small di_size), the directory data buffer is zero-length, causing a null-pointer dereference on the first read. 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's UFS/UFS2 filesystem image parser has a null-pointer dereference vulnerability. When parsing a crafted UFS image where the root inode (inode 2) is set to IFLNK (symlink) instead of IFDIR (directory), the parser unconditionally treats the root inode as a directory without checking its type. If the symlink has an embedded target with small di_size, the directory data buffer becomes zero-length, causing a null-pointer dereference on the first read operation.

MitigationUpgrade to NanaZip version 6.0.1698.0 or later. Avoid opening untrusted 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.1250.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. Verify NanaZip is installed
    Check for NanaZip installation in common locations such as C:\Program Files\NanaZip or C:\Program Files (x86)\NanaZip, or use system inventory to list installed applications containing 'NanaZip'
    Affected if NanaZip is present on the system
  2. Identify installed NanaZip version
    Right-click the NanaZip executable (e.g., NanaZip.exe), select Properties, and view the Version tab, or use PowerShell: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*NanaZip*'} | Select-Object DisplayName, DisplayVersion
    Affected if A version number is returned from the installation
  3. Compare version to affected range
    Parse the version number and compare: version >= 5.0.1250.0 AND version < 6.0.1698.0 indicates the vulnerable range. Version 6.0.1698.0 and later are patched.
    Affected if The installed version is 5.0.1250.0 through 6.0.1697.x (inclusive)
  4. Confirm UFS/UFS2 file handling capability
    NanaZip includes built-in support for UFS/UFS2 archive formats. Verify by attempting to open any .ufs or .ufs2 file in NanaZip, or check NanaZip's supported format list in the application.
    Affected if NanaZip can open or lists UFS/UFS2 as a supported format

If NanaZip is installed with version 5.0.1250.0 through 6.0.1697.x and can process UFS/UFS2 images, the environment is vulnerable to this CVE.

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 UFS/UFS2 filesystem images until the update is applied.

Recommended fix High confidence

6.0.1698.0

  1. Check current NanaZip version by launching the application or checking its properties
  2. Navigate to the official NanaZip GitHub releases page at github.com/M2Team/NanaZip
  3. Download the installer for version 6.0.1698.0 (the fixed release)
  4. Run the installer to upgrade from the current vulnerable version
  5. Verify the upgrade was successful by checking the installed version shows 6.0.1698.0 or later

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

Fix this in Nanazip Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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