CVE-2026-27114
DoS in M2Team Nanazip 5.0.1252.0 – 6.0.1630.0
Raw 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-27114 is a medium-severity Infinite Loop (CWE-835) vulnerability in M2Team Nanazip. Its CVSS base score is 5.1 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Application or System Exploitation (T1499.004); ranked at the 18th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-27114 affects NanaZip, an open-source file archiving utility, specifically in versions starting from 5.0.1252.0 up to but not including 6.0.1630.0. The vulnerability stems from circular `NextOffset` chains in the ROMFS archive parser, triggering an infinite loop (CWE-835: Loop with Unreachable Exit Condition). This issue has a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), indicating high severity primarily due to availability impact.
Attackers can exploit this remotely over a network with low complexity, requiring no privileges or user interaction beyond convincing a victim to open a malicious ROMFS archive file in an affected NanaZip version. Successful exploitation leads to a denial-of-service condition, as the infinite loop causes the application to hang or crash, consuming excessive CPU resources without impacting confidentiality or integrity.
The GitHub security advisory (GHSA-hfg9-6rf9-5pgx) from the M2Team/NanaZip repository details the issue, confirming that version 6.0.1630.0 includes a patch to resolve the infinite loop. A proof-of-concept exploit is available as a ZIP attachment, demonstrating the vulnerability for testing purposes. Security practitioners should prioritize updating to the patched version and scan for vulnerable installations.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-8315
Vulnerability Data
NanaZip is an open source file archive. Starting in version 5.0.1252.0 and prior to version 6.0.1630.0, circular `NextOffset` chains cause an infinite loop in the ROMFS archive parser. Version 6.0.1630.0 patches the issue.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover unreachable loop exit conditions through static analysis, fuzzing, or execution tracing.
Flaw remediation processes identify and correct infinite-loop defects reported from testing or operations.
Requiring documented development processes and secure coding standards reduces introduction of loops whose termination conditions are unreachable.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can uncover infinite-loop conditions before release.
Secure development life cycle mandates practices that can detect and prevent infinite-loop defects.
Application security requirements can specify loop-termination rules, indirectly reducing the weakness.
Secure coding standards directly address loop termination and prevent infinite loops.