{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-66913 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-66913 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-66913 is a medium-severity denial of service vulnerability in lookyloo, published on 28 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-66913 and fix it if it is affected.\n\nWhat it is: CVE-2026-66913 is a medium-severity denial of service vulnerability in lookyloo, published on 28 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-66913 in the wild and no public exploit code.\n\nAffected product: lookyloo. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-66913/ (Markdown: https://insights.sbomify.com/CVE-2026-66913/index.md)","id":"CVE-2026-66913","markdown":"https://insights.sbomify.com/CVE-2026-66913/index.md","name":"CVE-2026-66913","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Lookyloo web application","requires_auth":"none","summary":"Attackers can cause denial of service in Lookyloo by uploading zip bombs that exhaust memory during decompression.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CIRCL","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"Lookyloo did not enforce limits on the decompressed size of uploaded capture archives and compressed HAR files.\n\nAn 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.\n\nThe 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.\n\nThe patch introduces:\n\n  *  A 1 GB cumulative uncompressed-size limit for imported capture archives.\n  *  Size-limited gzip and zlib decompression for compressed HAR files.\n  *  Explicit detection and handling of suspected zip bombs.\n  *  An HTTP 400 response when an oversized compressed HAR file is submitted through the API.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Zip Bomb in Lookyloo Capture Upload Allows Denial of Service","id":"CVE-2026-66913","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Joomla Extension - seblod.com - Unauthenticated path traversal in SEBLOD \u003c 3.30.0, \u003c 4.7.0, \u003c 6.0.1","id":"CVE-2026-66914"},"packages":[],"prev":{"headline":"Stored Cross-Site Scripting in Zimbra","id":"CVE-2026-66912"},"products":["lookyloo"],"published":"2026-07-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-28","vendors":["lookyloo"]},"summary":"Attackers can cause denial of service in Lookyloo by uploading zip bombs that exhaust memory during decompression.","url":"https://insights.sbomify.com/CVE-2026-66913/"}