{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-42445 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-42445 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-42445 is a low-severity denial of service vulnerability in M2Team NanaZip, published on 12 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-42445 and fix it if it is affected.\n\nWhat it is: CVE-2026-42445 is a low-severity denial of service vulnerability in M2Team NanaZip, published on 12 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-42445 in the wild and no public exploit code.\n\nAffected product: M2Team NanaZip. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-42445/ (Markdown: https://insights.sbomify.com/CVE-2026-42445/index.md)","id":"CVE-2026-42445","markdown":"https://insights.sbomify.com/CVE-2026-42445/index.md","name":"CVE-2026-42445","record":{"aliases":["GHSA-jpf5-j78p-cp3x"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"NanaZip archive tool","requires_auth":"none","summary":"Attackers can crash NanaZip by providing a crafted UFS image with deep directory structures, causing stack exhaustion via uncontrolled recursion.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"nanazip","vendor":"m2team"}],"cvss":{"score":3.3,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-674","name":"Uncontrolled Recursion"}],"description":"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 UFS/UFS2 filesystem image parser in NanaZip. The function GetAllPaths recurses into subdirectories without any depth limit or visited-inode tracking. A crafted UFS image with a deep directory tree or an inode cycle causes stack exhaustion, crashing the NanaZip process. This vulnerability is fixed in 6.0.1698.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"NanaZip: Uncontrolled recursion in NanaZip UFS directory traversal causes stack exhaustion","id":"CVE-2026-42445","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"NanaZip: Stack out-of-bounds read in NanaZip ZealFS bitmap parser","id":"CVE-2026-42446"},"packages":[],"prev":{"headline":"NanaZip: Unbounded resource consumption in NanaZip littlefs parser via attacker-controlled BlockCount","id":"CVE-2026-42444"},"products":["NanaZip"],"published":"2026-05-12","related":[{"cvss_score":5.2,"headline":"NanaZip has DotNet Single file OOB Heap Read","id":"CVE-2026-26282","kev_date_added":null,"published":"2026-02-19"},{"cvss_score":5.1,"headline":"NanaZip .NET Single-File Manifest Parser Vulnerable to Out-of-Bounds Read via Unchecked RelativePathLength","id":"CVE-2026-27709","kev_date_added":null,"published":"2026-02-25"},{"cvss_score":5.1,"headline":"NanaZip .NET Single-File Parser Integer Underflow Leads to Unbounded Allocation (DoS)","id":"CVE-2026-27710","kev_date_added":null,"published":"2026-02-25"},{"cvss_score":5.1,"headline":"NanaZip UFS Archive Parser Memory Corruption via Unvalidated Directory Record Length","id":"CVE-2026-27711","kev_date_added":null,"published":"2026-02-25"},{"cvss_score":5.1,"headline":"NanZip has ROMFS Archive Infinite Loop / Stack Overflow","id":"CVE-2026-27014","kev_date_added":null,"published":"2026-02-19"},{"cvss_score":5.1,"headline":"NanaZip has ROMFS Archive Infinite Loop","id":"CVE-2026-27114","kev_date_added":null,"published":"2026-02-19"},{"cvss_score":4.4,"headline":"NanaZip: Stack out-of-bounds read in NanaZip ZealFS bitmap parser","id":"CVE-2026-42446","kev_date_added":null,"published":"2026-05-12"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-14","vendors":["M2Team"]},"summary":"Attackers can crash NanaZip by providing a crafted UFS image with deep directory structures, causing stack exhaustion via uncontrolled recursion.","url":"https://insights.sbomify.com/CVE-2026-42445/"}