CVE-2026-48104

GHSL-2026-120: 7-Zip SquashFS BlockToNode uninitialized heap read

MEDIUM
4.2
CVSS Score
Published: June 5, 2026 at 03:56 PM UTC
Updated: June 17, 2026 at 10:54 AM UTC
2 products affected across 2 vendorsZip 7-zip7-Zip

Using 7-Zip by mcmilk?

Get instant alerts when new vulnerabilities affect 7-Zip - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM4.2
Exploit prediction
EPSS 0.2%
SSVC
PoC

Description

7-Zip is a file archiver with a high compression ratio. Versions 9.18 through 26.00 contain an uninitialized heap read in the SquashFS archive handler caused by a sparsely populated index array. In the SquashFS handler, _blockToNode is allocated with capacity for every metadata block but populated only when an inode crosses a block boundary, so a crafted image with few inodes spanning many blocks leaves most slots holding raw heap contents (the underlying allocator does not zero-initialize POD storage). When OpenDir looks up an attacker-influenced blockIndex (derived from the RootInode superblock field), it reads two of these uninitialized slots and passes them as the left/right bounds of a binary search over _nodesPos, which dereferences the midpoint without bounds checking; if the resulting value happens to match the search key, the returned index is used to read a full node struct from _nodes whose fields feed further directory parsing, forming a chained OOB read primitive that is heap-layout-dependent and not reliably triggerable. The SquashFS handler is enabled by default in stock 7z.dll and the issue triggers during Open() with no interaction beyond opening the file; impact is denial of service from wild-pointer dereference and potential heap information disclosure, with no write primitive. Version 26.01 fixes the issue.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

9.18 ≤ v < 26.01
Affected range stops below 26.01, so it looks safe — our inference, not a vendor statement
v < 26.01
Affected range stops below 26.01, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

x_refsource_CONFIRMExploitPatchThird Party Advisory
Source: cverecord
https://securitylab.github.com/advisories/GHSL-2026-115_GHSL-2026-122_7-zip/

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

4.2MEDIUMGitHub_M
Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality
LOW
Integrity
NONE
Availability
LOW
Vector?

Quick Info

StatusANALYZED
CWE
CWE-908CWE-125

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card