Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-27709: CWE-125: Out-of-bounds Read in M2Team NanaZip

0
Medium
VulnerabilityCVE-2026-27709cvecve-2026-27709cwe-125
Published: Wed Feb 25 2026 (02/25/2026, 23:39:03 UTC)
Source: CVE Database V5
Vendor/Project: M2Team
Product: NanaZip

Description

CVE-2026-27709 is an out-of-bounds read vulnerability in the . NET Single File Application parser of NanaZip, an open-source file archiver. The flaw exists in versions from 5. 0. 1252. 0 up to but not including 6. 0. 1638. 0 and 6. 5.

AI-Powered Analysis

AILast updated: 02/26/2026, 00:13:44 UTC

Technical Analysis

CVE-2026-27709 is a medium-severity vulnerability classified under CWE-125 (Out-of-bounds Read) affecting NanaZip, a popular open-source file archiving tool developed by M2Team. The vulnerability resides in the .NET Single File Application parser component responsible for processing manifest data within archive bundles. Specifically, when parsing the RelativePathLength field in the manifest, a crafted archive can specify a malformed length value that causes the parser to read memory beyond the allocated HeaderBuffer. This out-of-bounds read leads to undefined behavior, including application crashes and the potential disclosure of sensitive in-process memory contents. The flaw affects NanaZip versions starting from 5.0.1252.0 up to versions prior to 6.0.1638.0 and 6.5.1638.0, which contain the fix. Exploitation requires the victim to open a maliciously crafted archive file, implying user interaction is necessary. The vulnerability requires low privileges (local access) and does not require authentication. The CVSS 4.0 vector indicates low attack complexity and no user privileges but does require user interaction. No known public exploits have been reported to date. The issue was publicly disclosed on February 25, 2026, with patches available in the latest NanaZip releases. This vulnerability could be leveraged by attackers to cause denial of service or leak sensitive memory data from the application process, potentially aiding further exploitation or information gathering.

Potential Impact

The primary impact of CVE-2026-27709 is the potential for denial of service through application crashes when processing malicious archives, which can disrupt normal operations for users relying on NanaZip for file extraction and archiving. Additionally, the out-of-bounds read may disclose sensitive memory contents from the process, potentially exposing confidential information or aiding attackers in crafting further attacks. While the vulnerability requires user interaction and local access, it poses a risk in environments where users frequently handle untrusted archive files, such as corporate networks, software development environments, and shared file repositories. The medium severity rating reflects moderate risk, but organizations with high-value data or strict availability requirements should prioritize remediation. Since NanaZip is open source and used globally, unpatched systems remain vulnerable to targeted attacks or accidental crashes caused by malformed archives.

Mitigation Recommendations

To mitigate CVE-2026-27709, organizations should immediately upgrade NanaZip to versions 6.0.1638.0 or later, where the vulnerability is fixed. If upgrading is not immediately feasible, users should avoid opening archive files from untrusted or unknown sources to reduce exposure. Implementing endpoint security solutions that scan archives for malicious content before extraction can help detect crafted bundles exploiting this flaw. Additionally, applying application whitelisting and restricting user permissions to prevent unauthorized software installation or execution can limit exploitation opportunities. Monitoring application logs for crashes related to NanaZip may help identify attempted exploitation. Developers and security teams should also consider sandboxing archive extraction processes to contain potential memory disclosures or crashes. Regularly reviewing and updating software dependencies and educating users about risks associated with opening unverified archives will further reduce risk.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-02-23T17:56:51.203Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 699f8c2fb7ef31ef0b6c21c5

Added to database: 2/25/2026, 11:56:31 PM

Last enriched: 2/26/2026, 12:13:44 AM

Last updated: 2/26/2026, 6:34:20 AM

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats