CVE-2026-54616 json
NanaZip: Heap out-of-bounds read in NanaZip SquashFS LZ4 decompressor via unchecked negative return value
published 4mo ago modified 24d ago also EUVD-2026-63481 , GHSA-95x5-qvvm-hmfp
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository M2Team/NanaZip. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 7.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 38%
- public exploits
- 0
- none known
Summary
NanaZip is the 7-Zip derivative intended for the modern Windows experience. From version 1.0.88.0 until stable version 6.0.1698.0 and preview version 6.5.1742.0, the Lz4Decode function in NanaZip.Core/SevenZip/CPP/7zip/Archive/SquashfsHandler.cpp rejects only a zero return from LZ4_decompress_safe even though malformed input produces a negative error value. The negative int is converted to the unsigned SizeT destLen and then truncated into outBufWasWrittenSize, causing ReadBlock to trust an attacker-inflated _cachedUnpackBlockSize. During fragment extraction, an attacker-controlled inode Offset can make memcpy read beyond the _cachedBlock heap allocation and place adjacent heap contents in the extracted file, or crash the process. This issue is fixed in stable version 6.0.1698.0 and preview version 6.5.1742.0.
Patch / fix
- m2team nanazip 6.0.1698.0, 6.5.1742.0
Is CVE-2026-54616 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2mo ago
Exploit prediction
0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/M2Team/NanaZip/security/advisories/GHSA-95x5-qvvm-hmfp referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:L |
Affected products
- M2Team NanaZip
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
References
- github.com /M2Team/NanaZip/commit/733e8570d2ba96c3e52aab44f5fd886775d5952f
- github.com /M2Team/NanaZip/commit/ce0322a1932e16a53e4a13e48bc61804c7826956
-
github.com
/M2Team/NanaZip/security/advisories/GHSA-95x5-qvvm-hmfp
exploit, advisory
- github.com /M2Team/NanaZip/releases/tag/6.0.1698.0
- github.com /M2Team/NanaZip/releases/tag/6.5.1742.0
Sources
- CVE List CVE-2026-54616
- NVD CVE-2026-54616
- Maintainer advisory GHSA-95x5-qvvm-hmfp
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of M2Team/NanaZip published their own advisory on GitHub. Reviewed sources take precedence over it.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.