{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27711 exists.","fix":"No fix has been published for CVE-2026-27711 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-27711 is a medium-severity memory corruption vulnerability in M2Team NanaZip, published on 25 Feb 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-27711 and fix it if it is affected.\n\nWhat it is: CVE-2026-27711 is a medium-severity memory corruption vulnerability in M2Team NanaZip, published on 25 Feb 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-27711 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-27711/ (Markdown: https://insights.sbomify.com/CVE-2026-27711/index.md)","id":"CVE-2026-27711","markdown":"https://insights.sbomify.com/CVE-2026-27711/index.md","name":"CVE-2026-27711","record":{"aliases":["GHSA-rjwv-4w7x-hc9c"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"NanaZip archive tool","requires_auth":"low_privilege","summary":"A crafted UFS archive file can trigger memory corruption in NanaZip, potentially allowing code execution or crashing the application.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"nanazip","vendor":"m2team"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"NanaZip is an open source file archive. Starting in version 5.0.1252.0 and prior to versions 6.0.1638.0 and 6.5.1638.0, a memory corruption vulnerability in NanaZip’s UFS parser allows a crafted `.ufs/.ufs2/.img` file to trigger out-of-bounds memory access during archive open/listing. The bug is reachable via normal user file-open flow and can cause process crash, hang, and potentially exploitable heap corruption. Versions 6.0.1638.0 and 6.5.1638.0 fix the issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"NanaZip UFS Archive Parser Memory Corruption via Unvalidated Directory Record Length","id":"CVE-2026-27711","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"OpenProject: Insufficient access control leads to create Wiki objects belongs unpermitted projects","id":"CVE-2026-27723"},"packages":[],"prev":{"headline":"NanaZip .NET Single-File Parser Integer Underflow Leads to Unbounded Allocation (DoS)","id":"CVE-2026-27710"},"products":["NanaZip"],"published":"2026-02-25","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":"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["M2Team"]},"summary":"A crafted UFS archive file can trigger memory corruption in NanaZip, potentially allowing code execution or crashing the application.","url":"https://insights.sbomify.com/CVE-2026-27711/"}