<?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, 21 Oct 2026 18:13:29 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-54427 — Apache bRPC: Stack Exhaustion via Unbounded Recursion in AMF Parser</title>
      <link>https://db.gcve.eu/vuln/cve-2026-54427</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache bRPC&lt;/p&gt;
&lt;p&gt;Uncontrolled recursion in the AMF parser in Apache bRPC &amp;lt; 1.18.0 allows a remote RTMP peer to crash a bRPC process by sending deeply nested AMF objects or arrays. The parser recursively processed nested AMF containers without enforcing a depth limit, which could exhaust the native stack.&lt;/p&gt;
&lt;p&gt;Affected Scenarios:
Applications using bRPC RTMP support and parsing AMF data from an untrusted RTMP peer. This includes RTMP servers parsing client command messages, RTMP clients parsing server responses or status messages, and either side parsing inbound AMF script data such as metadata or cue points. Direct callers of ReadAMFObject or ReadAMFArray on untrusted input are also affected.&lt;/p&gt;
&lt;p&gt;How to Fix:
1. Upgrade Apache bRPC to 1.18.0.
2. Apply the patch from PR  https://github.com/apache/brpc/pull/3344 .&lt;/p&gt;
&lt;p&gt;Note:
The fix introduces a configurable AMF nesting depth limit with default value 128. AMF objects or arrays deeper than amf_max_depth are rejected after applying the fix.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache bRPC&lt;/p&gt;
&lt;p&gt;Uncontrolled recursion in the AMF parser in Apache bRPC &amp;lt; 1.18.0 allows a remote RTMP peer to crash a bRPC process by sending deeply nested AMF objects or arrays. The parser recursively processed nested AMF containers without enforcing a depth limit, which could exhaust the native stack.&lt;/p&gt;
&lt;p&gt;Affected Scenarios:
Applications using bRPC RTMP support and parsing AMF data from an untrusted RTMP peer. This includes RTMP servers parsing client command messages, RTMP clients parsing server responses or status messages, and either side parsing inbound AMF script data such as metadata or cue points. Direct callers of ReadAMFObject or ReadAMFArray on untrusted input are also affected.&lt;/p&gt;
&lt;p&gt;How to Fix:
1. Upgrade Apache bRPC to 1.18.0.
2. Apply the patch from PR  https://github.com/apache/brpc/pull/3344 .&lt;/p&gt;
&lt;p&gt;Note:
The fix introduces a configurable AMF nesting depth limit with default value 128. AMF objects or arrays deeper than amf_max_depth are rejected after applying the fix.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-54427</guid>
    </item>
  </channel>
</rss>
