<?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://db.gcve.eu</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>Wed, 28 Oct 2026 15:38:58 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-65627 — Decompression bomb via unbounded zlib:inflate in jose_jwe_zip:uncompress/2</title>
      <link>https://db.gcve.eu/vuln/cve-2026-65627</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; potatosalad jose&lt;/p&gt;
&lt;p&gt;Improper Handling of Highly Compressed Data (Data Amplification) vulnerability in potatosalad jose (erlang-jose) allows a remote attacker to exhaust a node&amp;#39;s memory with a small crafted JWE token.&lt;/p&gt;
&lt;p&gt;The jose_jwe_zip:uncompress/2 function in src/jwe/jose_jwe_zip.erl decompresses the DEFLATE-compressed plaintext of a JWE that carries the optional zip: DEF header by calling zlib:inflate/2 on the entire attacker-controlled stream, with no bound on the output size or the inflation ratio. Raw DEFLATE reaches ratios around 1000:1 on highly repetitive input, so a few-kilobyte token inflates to hundreds of megabytes or gigabytes in a single call.&lt;/p&gt;
&lt;p&gt;Decompression runs automatically during decryption through jose_jwe:block_decrypt/2 (JOSE.JWE.block_decrypt/2 in Elixir), before the recipient can inspect or reject the payload. With the common asymmetric key-management algorithms (RSA-OAEP, ECDH-ES) an attacker needs only the recipient&amp;#39;s public key to craft such a token, so no authentication or secret material is required. A single small token can exhaust the node&amp;#39;s memory and crash the BEAM, denying service to all users.&lt;/p&gt;
&lt;p&gt;This issue affects jose: from 1.0.0 before 1.11.13.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; potatosalad jose&lt;/p&gt;
&lt;p&gt;Improper Handling of Highly Compressed Data (Data Amplification) vulnerability in potatosalad jose (erlang-jose) allows a remote attacker to exhaust a node&amp;#39;s memory with a small crafted JWE token.&lt;/p&gt;
&lt;p&gt;The jose_jwe_zip:uncompress/2 function in src/jwe/jose_jwe_zip.erl decompresses the DEFLATE-compressed plaintext of a JWE that carries the optional zip: DEF header by calling zlib:inflate/2 on the entire attacker-controlled stream, with no bound on the output size or the inflation ratio. Raw DEFLATE reaches ratios around 1000:1 on highly repetitive input, so a few-kilobyte token inflates to hundreds of megabytes or gigabytes in a single call.&lt;/p&gt;
&lt;p&gt;Decompression runs automatically during decryption through jose_jwe:block_decrypt/2 (JOSE.JWE.block_decrypt/2 in Elixir), before the recipient can inspect or reject the payload. With the common asymmetric key-management algorithms (RSA-OAEP, ECDH-ES) an attacker needs only the recipient&amp;#39;s public key to craft such a token, so no authentication or secret material is required. A single small token can exhaust the node&amp;#39;s memory and crash the BEAM, denying service to all users.&lt;/p&gt;
&lt;p&gt;This issue affects jose: from 1.0.0 before 1.11.13.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-65627</guid>
    </item>
  </channel>
</rss>
