LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27711: NanaZip UFS Archive Parser Memory Corruption via Unvalidated Directory Record Length

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.

MediumCVSS 5.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-27711 affects NanaZip when a user opens or lists a specially crafted UFS, UFS2, or IMG archive. The main expected impact is a crash or hang, but the advisory notes potentially exploitable heap corruption. This is not reported as actively exploited in the provided sources.

Executive priority

Treat as a targeted user-file handling risk. Prioritize updating endpoints where NanaZip is installed and users handle externally sourced archives or disk images. Business urgency is moderate because exploitation needs user interaction, but crashes and potential memory corruption justify prompt remediation.

Technical view

NanaZip versions 5.0.1252.0 through below 6.0.1638.0, and 6.1 through below 6.5.1638.0, contain memory corruption in the UFS archive parser. An unvalidated directory record length can cause out-of-bounds memory access during normal archive open/listing. CVSS 4.0 score is 5.1, with local attack vector and user interaction required.

Likely exposure

Exposure is limited to systems with affected NanaZip versions where users may open untrusted .ufs, .ufs2, or .img files. The CVSS vector indicates local access, low complexity, privileges required, and user interaction required.

Exploitation context

The provided sources do not show active exploitation or KEV listing. Exploitation requires a crafted archive and a user-driven open/listing action. Reported outcomes include process crash, hang, and possible heap corruption.

Researcher notes

Evidence is limited to the CVE record and vendor GitHub advisory. The weakness is listed as CWE-125, although the description also references heap corruption. Do not assume remote, wormable, or confirmed code execution behavior from the provided sources.

Mitigation direction

  • Upgrade NanaZip to 6.0.1638.0 or 6.5.1638.0, as applicable.
  • Avoid opening untrusted .ufs, .ufs2, or .img files until updated.
  • Check the GitHub advisory for any newer vendor guidance.

Validation and detection

  • Inventory NanaZip installations and record exact version numbers.
  • Confirm affected ranges: >=5.0.1252.0 <6.0.1638.0 or >=6.1 <6.5.1638.0.
  • Verify updated systems report version 6.0.1638.0 or 6.5.1638.0.
  • Review endpoint telemetry for NanaZip crashes involving UFS, UFS2, or IMG files.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-125: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-27711 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.1 (4.0)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.1CVSS 4.0MediumCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

5.1Medium
CVSS 4.0 vector shape for CVE-2026-27711Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
M2TeamNanaZip>= 5.0.1252.0, < 6.0.1638.0, >= 6.1, < 6.5.1638.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.