Description
Lookyloo did not enforce limits on the decompressed size of uploaded capture archives and compressed HAR files.

An attacker could submit a specially crafted ZIP, gzip, or zlib-compressed capture containing data that expands to a very large size during processing. Because the application decompressed this content directly in memory without first limiting the output size, processing the malicious capture could exhaust available memory, terminate a web or worker process, or make the Lookyloo instance unavailable.

The vulnerability affects both full Lookyloo capture archive imports and API submissions containing gzip-compressed HAR data. Repeated exploitation could cause a persistent denial-of-service condition until the affected processes or instance are restarted.

The patch introduces:

* A 1 GB cumulative uncompressed-size limit for imported capture archives.
* Size-limited gzip and zlib decompression for compressed HAR files.
* Explicit detection and handling of suspected zip bombs.
* An HTTP 400 response when an oversized compressed HAR file is submitted through the API.
Published: 2026-07-28
Score: 6.9 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability in Lookyloo arises from a lack of limits on the decompressed size of uploaded capture archives and compressed HAR files. An attacker can craft a ZIP, gzip, or zlib archive that expands to a very large size when decompressed in memory. This can exhaust available memory, crash web or worker processes, or render the Lookyloo instance unavailable. The weakness is described by CWE-400, representing insufficient limits on resource consumption.

Affected Systems

The impacted product is Lookyloo from the vendor lookyloo. Version information is not supplied in the advisory, so all current releases up to the patch are considered vulnerable until a fixed release is deployed.

Risk and Exploitability

The CVSS score of 6.9 indicates a moderate severity. The EPSS score is below 1%, suggesting low likelihood of widespread exploitation, and the vulnerability is not listed in CISA’s KEV catalog. However, attackers can use the public upload or API endpoints to deliver specially crafted compressed files. If exploited repeatedly, the system can enter a persistent denial-of-service state until processes or the instance are restarted.

Generated by OpenCVE AI on August 3, 2026 at 15:10 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Lookyloo to the patched release that enforces a 1 GB uncompressed-size limit for capture archives and compressed HAR files.
  • If an upgrade is not immediately feasible, configure the upload API or reverse proxy to reject files that exceed a safe uncompressed size threshold by limiting content length or using middleware that checks decompressed size before processing.
  • Deploy process resource limits (e.g., ulimit or cgroups) to cap the memory usage of Lookyloo worker processes, and set up monitoring to detect memory exhaustion and trigger automated restarts.

Generated by OpenCVE AI on August 3, 2026 at 15:10 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 28 Jul 2026 20:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Tue, 28 Jul 2026 20:15:00 +0000

Type Values Removed Values Added
First Time appeared Lookyloo
Lookyloo lookyloo
Vendors & Products Lookyloo
Lookyloo lookyloo

Tue, 28 Jul 2026 16:15:00 +0000

Type Values Removed Values Added
Description Lookyloo did not enforce limits on the decompressed size of uploaded capture archives and compressed HAR files. An attacker could submit a specially crafted ZIP, gzip, or zlib-compressed capture containing data that expands to a very large size during processing. Because the application decompressed this content directly in memory without first limiting the output size, processing the malicious capture could exhaust available memory, terminate a web or worker process, or make the Lookyloo instance unavailable. The vulnerability affects both full Lookyloo capture archive imports and API submissions containing gzip-compressed HAR data. Repeated exploitation could cause a persistent denial-of-service condition until the affected processes or instance are restarted. The patch introduces: * A 1 GB cumulative uncompressed-size limit for imported capture archives. * Size-limited gzip and zlib decompression for compressed HAR files. * Explicit detection and handling of suspected zip bombs. * An HTTP 400 response when an oversized compressed HAR file is submitted through the API.
Title Zip Bomb in Lookyloo Capture Upload Allows Denial of Service
Weaknesses CWE-400
References
Metrics cvssV4_0

{'score': 6.9, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N'}


Subscriptions

Lookyloo Lookyloo
cve-icon MITRE

Status: PUBLISHED

Assigner: CIRCL

Published:

Updated: 2026-07-28T19:20:16.204Z

Reserved: 2026-07-28T12:19:10.431Z

Link: CVE-2026-66913

cve-icon Vulnrichment

Updated: 2026-07-28T19:20:10.263Z

cve-icon NVD

Status : Deferred

Published: 2026-07-28T13:19:06.530

Modified: 2026-07-30T16:55:34.270

Link: CVE-2026-66913

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-03T15:15:04Z

Weaknesses
  • CWE-400

    Uncontrolled Resource Consumption