<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 16:14:22 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-342198</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-342198</link>
      <description>EUVD-2026-342198</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-342198</guid>
    </item>
    <item>
      <title>fkie_cve-2026-66913</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-66913</link>
      <description>&lt;p&gt;Lookyloo did not enforce limits on the decompressed size of uploaded capture archives and compressed HAR files.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The patch introduces:&lt;/p&gt;
&lt;p&gt;*  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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Lookyloo did not enforce limits on the decompressed size of uploaded capture archives and compressed HAR files.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The patch introduces:&lt;/p&gt;
&lt;p&gt;*  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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-66913</guid>
    </item>
  </channel>
</rss>
