CVE-2026-26282: CWE-126: Buffer Over-read in M2Team NanaZip
NanaZip is an open source file archive Starting in version 5.0.1252.0 and prior to version 6.0.1630.0, NanaZip has an out-of-bounds heap read in `.NET Single File` bundle header parser due to missing bounds check. Opening a crafted file with NanaZip causes a crash or leaks heap data to the user. Version 6.0.1630.0 patches the issue.
AI Analysis
Technical Summary
CVE-2026-26282 is a buffer over-read vulnerability classified under CWE-126, affecting the open-source file archiver NanaZip. The vulnerability arises from a missing bounds check in the .NET Single File bundle header parser component of NanaZip versions starting from 5.0.1252.0 up to but not including 6.0.1630.0. When a user opens a specially crafted archive file, the parser reads beyond the allocated heap buffer, resulting in an out-of-bounds heap read. This can cause the application to crash or leak sensitive heap data to the user, potentially exposing information that resides in memory during parsing. The vulnerability requires the attacker to have local access with limited privileges and for the user to interact by opening the malicious file. No authentication beyond limited privileges is needed, and no network vector is involved. The CVSS 4.0 base score is 5.2, reflecting medium severity due to the limited attack vector and user interaction requirement. The flaw has not been reported exploited in the wild. The issue was addressed and patched in NanaZip version 6.0.1630.0 by adding proper bounds checking in the parser to prevent out-of-bounds reads.
Potential Impact
The primary impact of this vulnerability is the potential for application crashes, leading to denial of service for the user running NanaZip. More critically, the out-of-bounds read can leak heap memory contents, which may include sensitive information such as file metadata, user data, or other in-memory secrets depending on the environment and usage context. Although the attacker requires local access and user interaction, this vulnerability could be leveraged in targeted attacks where malicious archive files are delivered via phishing or social engineering. Organizations relying on NanaZip for file archiving and extraction may face operational disruptions and risk of information disclosure. The scope is limited to affected versions and local users, but the risk is non-negligible in environments where untrusted files are handled frequently. Since no known exploits exist in the wild, the immediate threat is moderate, but the vulnerability should be addressed promptly to prevent future exploitation.
Mitigation Recommendations
Organizations should upgrade NanaZip to version 6.0.1630.0 or later, where the vulnerability is patched. Until the update can be applied, users should avoid opening untrusted or suspicious archive files with affected versions of NanaZip. Implement endpoint security controls to detect and block malicious archive files and monitor for abnormal application crashes. Employ user training to recognize phishing attempts that may deliver crafted archives. Restrict local user privileges where possible to limit the ability to execute or open untrusted files. Additionally, consider using alternative, unaffected archiving tools for handling untrusted files. Regularly audit and update software dependencies to minimize exposure to known vulnerabilities.
Affected Countries
United States, Germany, Japan, South Korea, United Kingdom, Canada, France, Australia, Netherlands, China
CVE-2026-26282: CWE-126: Buffer Over-read in M2Team NanaZip
Description
NanaZip is an open source file archive Starting in version 5.0.1252.0 and prior to version 6.0.1630.0, NanaZip has an out-of-bounds heap read in `.NET Single File` bundle header parser due to missing bounds check. Opening a crafted file with NanaZip causes a crash or leaks heap data to the user. Version 6.0.1630.0 patches the issue.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-26282 is a buffer over-read vulnerability classified under CWE-126, affecting the open-source file archiver NanaZip. The vulnerability arises from a missing bounds check in the .NET Single File bundle header parser component of NanaZip versions starting from 5.0.1252.0 up to but not including 6.0.1630.0. When a user opens a specially crafted archive file, the parser reads beyond the allocated heap buffer, resulting in an out-of-bounds heap read. This can cause the application to crash or leak sensitive heap data to the user, potentially exposing information that resides in memory during parsing. The vulnerability requires the attacker to have local access with limited privileges and for the user to interact by opening the malicious file. No authentication beyond limited privileges is needed, and no network vector is involved. The CVSS 4.0 base score is 5.2, reflecting medium severity due to the limited attack vector and user interaction requirement. The flaw has not been reported exploited in the wild. The issue was addressed and patched in NanaZip version 6.0.1630.0 by adding proper bounds checking in the parser to prevent out-of-bounds reads.
Potential Impact
The primary impact of this vulnerability is the potential for application crashes, leading to denial of service for the user running NanaZip. More critically, the out-of-bounds read can leak heap memory contents, which may include sensitive information such as file metadata, user data, or other in-memory secrets depending on the environment and usage context. Although the attacker requires local access and user interaction, this vulnerability could be leveraged in targeted attacks where malicious archive files are delivered via phishing or social engineering. Organizations relying on NanaZip for file archiving and extraction may face operational disruptions and risk of information disclosure. The scope is limited to affected versions and local users, but the risk is non-negligible in environments where untrusted files are handled frequently. Since no known exploits exist in the wild, the immediate threat is moderate, but the vulnerability should be addressed promptly to prevent future exploitation.
Mitigation Recommendations
Organizations should upgrade NanaZip to version 6.0.1630.0 or later, where the vulnerability is patched. Until the update can be applied, users should avoid opening untrusted or suspicious archive files with affected versions of NanaZip. Implement endpoint security controls to detect and block malicious archive files and monitor for abnormal application crashes. Employ user training to recognize phishing attempts that may deliver crafted archives. Restrict local user privileges where possible to limit the ability to execute or open untrusted files. Additionally, consider using alternative, unaffected archiving tools for handling untrusted files. Regularly audit and update software dependencies to minimize exposure to known vulnerabilities.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-02-12T17:10:53.414Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 699812af2c4d84f260aeb044
Added to database: 2/20/2026, 7:52:15 AM
Last enriched: 2/28/2026, 2:20:39 PM
Last updated: 4/6/2026, 9:39:49 AM
Views: 95
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.