<?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://vulnerability.circl.lu</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>Mon, 28 Sep 2026 19:47:12 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-48853 — Remote code execution and denial of service via unsafe Erlang term deserialization in elixir-grpc/grpc</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-48853</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; elixir-grpc grpc&lt;/p&gt;
&lt;p&gt;Deserialization of Untrusted Data and Allocation of Resources Without Limits or Throttling vulnerabilities in elixir-grpc grpc allow unauthenticated attackers to crash the BEAM node via atom table exhaustion and, when a decoded term flows into a call site that invokes it, achieve remote code execution on the server.&lt;/p&gt;
&lt;p&gt;&amp;#39;Elixir.GRPC.Codec.Erlpack&amp;#39;:decode/2 (lib/grpc/codec/erlpack.ex) calls :erlang.binary_to_term/1 on the raw gRPC message body without the :safe option, no size bound, and no type guard. Any unauthenticated peer that sends a request with Content-Type: application/grpc+erlpack can send a crafted payload that mints arbitrary new atoms (which are never garbage-collected, exhausting the bounded atom table and crashing the VM) or that encodes a fun term which, if applied anywhere downstream, executes attacker-controlled code inside the server process.&lt;/p&gt;
&lt;p&gt;This issue affects grpc: from 0.4.0 before 1.0.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; elixir-grpc grpc&lt;/p&gt;
&lt;p&gt;Deserialization of Untrusted Data and Allocation of Resources Without Limits or Throttling vulnerabilities in elixir-grpc grpc allow unauthenticated attackers to crash the BEAM node via atom table exhaustion and, when a decoded term flows into a call site that invokes it, achieve remote code execution on the server.&lt;/p&gt;
&lt;p&gt;&amp;#39;Elixir.GRPC.Codec.Erlpack&amp;#39;:decode/2 (lib/grpc/codec/erlpack.ex) calls :erlang.binary_to_term/1 on the raw gRPC message body without the :safe option, no size bound, and no type guard. Any unauthenticated peer that sends a request with Content-Type: application/grpc+erlpack can send a crafted payload that mints arbitrary new atoms (which are never garbage-collected, exhausting the bounded atom table and crashing the VM) or that encodes a fun term which, if applied anywhere downstream, executes attacker-controlled code inside the server process.&lt;/p&gt;
&lt;p&gt;This issue affects grpc: from 0.4.0 before 1.0.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-48853</guid>
    </item>
  </channel>
</rss>
