dbcve.org
NanazipApplication · M2team

CVE-2026-42355

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 uncontrolled recursion vulnerability exists in the Electron Archive (ASAR) parser in NanaZip. When opening a crafted .asar file with deeply nested JSON in the header, both nlohmann::json::parse and the handler's GetAllPaths function recurse without depth limits, exhausting the thread stack and crashing the NanaZip process. 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 contains an uncontrolled recursion vulnerability in its Electron Archive (ASAR) parser. When parsing a crafted .asar file with deeply nested JSON in the header, both nlohmann::json::parse and the GetAllPaths function recurse without depth limits, causing stack exhaustion and process crash (Denial of Service).

MitigationUpgrade NanaZip to version 6.0.1698.0 or later. Avoid opening untrusted .asar files until the upgrade 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. Locate the installed NanaZip version
    Open NanaZip, then navigate to Help > About NanaZip (or check the application's version property in Windows Settings > Apps > Apps & features). Alternatively, right-click the NanaZip executable file, select Properties, and check the Details tab for the Product version.
    Affected if The displayed version falls within the range >= 5.0.1250.0 and < 6.0.1698.0, indicating the installation is affected by the uncontrolled recursion vulnerability.
  2. Confirm NanaZip is the installed product
    Verify that the application name displayed in the About window or Properties is specifically NanaZip (by M2team), as other archive utilities may share similar names but have different version numbering.
    Affected if The product is confirmed as NanaZip by M2team with a version number matching the affected range.
  3. Determine if ASAR file handling is in use
    Check if users within the organization routinely open or extract .asar files using NanaZip. ASAR files are Electron archive formats commonly used to bundle application code.
    Affected if The affected version of NanaZip is actively used to handle .asar files, exposing the environment to the vulnerability when processing untrusted .asar archives.

A system is affected if NanaZip version 5.0.1250.0 through 6.0.1697.x is installed and used to process .asar files, as the vulnerability exists in the ASAR parser's handling of deeply nested JSON headers.

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 NanaZip to version 6.0.1698.0 or later. Avoid opening untrusted .asar files until the upgrade is applied.

Recommended fix High confidence

6.0.1698.0

  1. 1. Download NanaZip version 6.0.1698.0 or later from the official GitHub repository (github.com)
  2. 2. Verify the downloaded installer checksum matches the published checksum
  3. 3. Close any running instances of NanaZip
  4. 4. Install the new version, or extract and replace the existing installation
  5. 5. Test that NanaZip can open and extract normal .asar files without crashing
  6. 6. Verify the application runs without errors after the upgrade
Caveat Major version upgrade from 5.x to 6.x may include interface or functionality changes; review release notes for breaking changes before production deployment

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

Fix this in Nanazip Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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