<?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>Tue, 10 Nov 2026 05:30:09 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-71397</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-71397</link>
      <description>&lt;p&gt;Allocation of Resources Without Limits or Throttling vulnerability in elixir-grpc grpc_server allows unauthenticated attackers to exhaust memory and crash the node via an oversized client-streaming or bidirectional-streaming request body.&lt;/p&gt;
&lt;p&gt;The streaming read clause of &amp;#39;Elixir.GRPC.Server.Adapters.Cowboy.Handler&amp;#39;:info/3 (grpc_server/lib/grpc/server/adapters/cowboy/handler.ex) never checks the configured max_body_size. Only the unary read path enforces that cap. &amp;#39;Elixir.GRPC.Server.Adapters.Cowboy&amp;#39;:reading_stream/1 (grpc_server/lib/grpc/server/adapters/cowboy.ex) appends every received chunk to its buffer until a complete length-prefixed message arrives. A client can declare a very large message and send it across many small HTTP/2 DATA frames, and the server buffers all of it.&lt;/p&gt;
&lt;p&gt;This issue affects grpc_server: from 1.0.0 before 1.0.6.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Allocation of Resources Without Limits or Throttling vulnerability in elixir-grpc grpc_server allows unauthenticated attackers to exhaust memory and crash the node via an oversized client-streaming or bidirectional-streaming request body.&lt;/p&gt;
&lt;p&gt;The streaming read clause of &amp;#39;Elixir.GRPC.Server.Adapters.Cowboy.Handler&amp;#39;:info/3 (grpc_server/lib/grpc/server/adapters/cowboy/handler.ex) never checks the configured max_body_size. Only the unary read path enforces that cap. &amp;#39;Elixir.GRPC.Server.Adapters.Cowboy&amp;#39;:reading_stream/1 (grpc_server/lib/grpc/server/adapters/cowboy.ex) appends every received chunk to its buffer until a complete length-prefixed message arrives. A client can declare a very large message and send it across many small HTTP/2 DATA frames, and the server buffers all of it.&lt;/p&gt;
&lt;p&gt;This issue affects grpc_server: from 1.0.0 before 1.0.6.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-71397</guid>
    </item>
  </channel>
</rss>
