{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55780 exists.","fix":"No fix has been published for CVE-2026-55780 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-55780 is a low-severity denial of service vulnerability in M2Team NanaZip, published on 10 Jul 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-55780 and fix it if it is affected.\n\nWhat it is: CVE-2026-55780 is a low-severity denial of service vulnerability in M2Team NanaZip, published on 10 Jul 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55780 exists.\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-55780/ (Markdown: https://insights.sbomify.com/CVE-2026-55780/index.md)","id":"CVE-2026-55780","markdown":"https://insights.sbomify.com/CVE-2026-55780/index.md","name":"CVE-2026-55780","record":{"aliases":["GHSA-ppm9-5267-rq72"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Windows archive utility","requires_auth":"low_privilege","summary":"A crafted .NET single-file bundle can cause an unhandled exception and crash NanaZip due to unvalidated entry size fields.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":2.4,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"},{"id":"CWE-248","name":"Uncaught Exception"}],"description":"NanaZip is the 7-Zip derivative intended for the modern Windows experience. Prior to 6.5.1749.0, NanaZip's .NET single-file bundle handler in NanaZip.Codecs.Archive.DotNetSingleFile.cpp sizes its extraction buffer from the bundle entry Size field, which is only checked for sign and is not validated against the real file size. A crafted bundle can cause an attacker-chosen allocation inside Extract, where std::bad_alloc or std::length_error can escape across the COM STDMETHODCALLTYPE boundary and crash the process. This issue is fixed in version 6.5.1749.0.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2026-08-17","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-08-17","kind":"exploitdb","ref":"52652","stars":null,"title":"NanaZip 6.5  -  DoS"}],"tier":"weaponised"},"has_fix":false,"headline":"NanaZip: Uncaught exception / unbounded allocation in NanaZip .NET single-file Extract() via unvalidated entry Size","id":"CVE-2026-55780","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"NanaZip: Unbounded memory allocation (DoS) in NanaZip UFS parser via unvalidated fs_bsize/fs_fsize superblock fields","id":"CVE-2026-55781"},"packages":[],"prev":{"headline":"Silverstripe Versioned: XSS in archive admin restore","id":"CVE-2026-55779"},"products":["NanaZip"],"published":"2026-07-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-13","vendors":["M2Team"]},"summary":"A crafted .NET single-file bundle can cause an unhandled exception and crash NanaZip due to unvalidated entry size fields.","url":"https://insights.sbomify.com/CVE-2026-55780/"}