Uninitialized memory disclosure in the 7-Zip SquashFS handler

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-104086?

CVE-2026-104086 is a vulnerability classified as Use of Uninitialized Resource, affecting 7-Zip (affected versions: < 26.03). This vulnerability is rated Medium, with a CVSS score of 6.8. There is not enough data to determine whether this vulnerability has been exploited.

Overview

Original source data

7-Zip before 26.03 contains an uninitialized memory disclosure vulnerability in the SquashFS v4 archive handler (SquashfsHandler.cpp) that allows attackers to leak heap memory by crafting a malicious archive where the superblock’s no_ids field is set so that the final metadata block’s expected size is miscomputed and bypasses the size validation check. By listing or extracting the crafted archive, attackers can cause the application to return uninitialized heap memory as the kpidUserId and kpidGroupId properties, exposing potentially sensitive process memory contents to the user.

Affected products and scope

According to the normalized affected data:

  • 7-Zip: releases before 26.03 are affected. The range is represented as version 0 with lessThan: 26.03 and status affected.
  • The product's default status is recorded as unaffected outside the affected range above.
  • No additional product branch or configuration-specific affected scope is identified in the record.

Technical details

7-Zip has a flaw in its SquashFS v4 archive handler, specifically SquashfsHandler.cpp. A malicious archive can set the superblock's no_ids field so that the expected size of the final metadata block is miscomputed and the size validation check is bypassed. When the archive is listed or extracted, the handler can return uninitialized heap memory as the kpidUserId and kpidGroupId properties, exposing memory contents to the user. The weakness is classified as CWE-908, Use of Uninitialized Resource. The supplied assessment describes local reachability, no required privileges, low complexity, and passive user interaction. The record does not establish which exact bytes or data will be disclosed in any particular processing event.

Exploitability

The supplied assessment characterizes exploitation as local, requiring no special privileges and having low complexity. An attacker must provide a crafted archive, and a user or process must list or extract it before the vulnerable code path is reached. User interaction is described as passive, although archive processing remains a necessary condition. The record does not establish active exploitation, a public exploit, or ransomware use; those statuses are unspecified or empty in the supplied data.

Technical impact

The technical outcome is that data from uninitialized heap memory may be returned through the kpidUserId and kpidGroupId properties, causing process memory contents to be exposed to the user. This is primarily a confidentiality issue; the record does not establish an integrity or availability effect and does not describe code execution.

  • The practical exposure depends on what data is present in the heap when the archive is processed.
  • The most relevant organizational risk is in workflows that open archives from external sources or shared inputs.
  • A single processing event that reveals no obvious data should not be treated as proof that other events are safe.

Business impact

The flaw may expose sensitive data present in the 7-Zip process heap to the user performing the archive operation. Depending on timing and memory contents, the disclosure could include transient information or secrets handled by the process, but the record does not confirm a specific data type.

  • The primary concern is for workstations, servers, or automated workflows that process archives from external or untrusted sources.
  • The documented effect is a confidentiality disclosure; the record identifies no integrity or availability impact.
  • The record does not describe code execution, data modification, service disruption, a named victim, or a confirmed breach scenario.

Remediation

  1. Upgrade 7-Zip to 26.03. This is the first boundary outside the normalized affected range and is identified by the CNA reference as the fixed release.
  2. Until the update is complete, avoid using affected installations to list or extract untrusted SquashFS archives. If the workflow cannot be paused, restrict inputs to trusted sources and process them in a controlled environment as a precaution.
  3. After updating, recheck standalone installations, portable copies, and integrated components to ensure that no binary within the affected range is still used by archive-processing workflows.

Detection

  1. Inventory every 7-Zip installation, portable copy, bundled binary, and plugin, and record the actual version of each binary.
  2. Identify workstations, servers, or automated workflows that accept untrusted archives and use SquashFS listing or extraction.
  3. Where archive-property telemetry is available, review unusual results involving kpidUserId and kpidGroupId as a triage signal. This is a precautionary review, not a confirmed indicator of compromise.
  4. Review audit records or telemetry for suspicious archive open, listing, and extraction activity while affected installations were in use. No specific log event or IOC is supplied, and the absence of log evidence does not prove that a system is safe.
Sources (7)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.