CVE-2026-54616Network attack vector

Heap out-of-bounds read via negative LZ4 return

Published Aug 20, 2026 · Updated Aug 20, 2026

Out-of-bounds read in NanaZip before 6.0.1698.0 and 6.5.1742.0 allows remote attackers to read heap data or crash NanaZip with a crafted SquashFS archive. In SquashfsHandler.cpp, Lz4Decode rejects only a zero return from LZ4_decompress_safe; a negative error value is cast to SizeT, which inflates the cached unpacked-block length that ReadBlock later trusts during fragment extraction. Exploitation requires a user to open or extract an attacker-supplied archive, after which a controlled inode offset can drive memcpy past the heap buffer and copy adjacent heap bytes into the output file or terminate the process.

CVSS severity7.1
High
EPSS probability0.32%
Next 30 days · Sep 17, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Out-of-bounds read in NanaZip before 6.0.1698.0 and 6.5.1742.0 allows remote attackers to read heap data or crash NanaZip with a crafted SquashFS archive. In SquashfsHandler.cpp, Lz4Decode rejects only a zero return from LZ4_decompress_safe; a negative error value is cast to SizeT, which inflates the cached unpacked-block length that ReadBlock later trusts during fragment extraction. Exploitation requires a user to open or extract an attacker-supplied archive, after which a controlled inode offset can drive memcpy past the heap buffer and copy adjacent heap bytes into the output file or terminate the process.

The record

CVE
CVE-2026-54616
Published
Aug 20, 2026
Updated
Aug 20, 2026
Vendor
M2-Team
Product
NanaZip
Classifications
CWE-125, T1203
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 20, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 20, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 1.0.88.0, < 6.0.1698.0
  2. Affected versionversion=>= 6.5.1638.0, < 6.5.1742.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

M2-Team · NanaZipversion=>= 1.0.88.0, < 6.0.1698.0; version=>= 6.5.1638.0, < 6.5.1742.0

Published CVSS scores

7.1GitHub Advisory DatabaseCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:L

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 11, 2026Sep 17, 2026
Latest reporting daySep 17, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-125Out-of-bounds Read
T1203Exploitation for Client Execution

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo