<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-23T07:03:34.717914+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-54426</id>
    <title>fkie_cve-2026-54426</title>
    <updated>2026-10-23T07:03:34.970303+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>Uncontrolled recursion in the Redis reply parser in Apache bRPC &lt; 1.18.0 allows a remote Redis server peer to crash a bRPC Redis client process by returning a deeply nested RESP array reply. The parser recursed once for each nested array level without enforcing a depth limit. The fix adds a configurable Redis reply depth limit with default value 128 and rejects replies exceeding that limit.</p>
<p>Affected Scenarios:
Applications using bRPC as a Redis client with ChannelOptions.protocol="redis" and receiving replies from an untrusted or faulty Redis server peer.</p>
<p>How to Fix:
1. Upgrade Apache bRPC to 1.18.0.
2. Apply the patch from PR  https://github.com/apache/brpc/pull/3344 .</p>
<p>Note:
After applying the fix, Redis replies with array nesting deeper than redis_max_reply_depth are rejected.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-54426"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-m7v5-m3p2-6w26</id>
    <title>GHSA-m7v5-m3p2-6w26</title>
    <updated>2026-10-23T07:03:34.970439+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>Uncontrolled recursion in the Redis reply parser in Apache bRPC &lt; 1.18.0 allows a remote Redis server peer to crash a bRPC Redis client process by returning a deeply nested RESP array reply. The parser recursed once for each nested array level without enforcing a depth limit. The fix adds a configurable Redis reply depth limit with default value 128 and rejects replies exceeding that limit.</p>
<p>Affected Scenarios:
Applications using bRPC as a Redis client with ChannelOptions.protocol="redis" and receiving replies from an untrusted or faulty Redis server peer.</p>
<p>How to Fix:
1. Upgrade Apache bRPC to 1.18.0.
2. Apply the patch from PR  https://github.com/apache/brpc/pull/3344 .</p>
<p>Note:
After applying the fix, Redis replies with array nesting deeper than redis_max_reply_depth are rejected.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-m7v5-m3p2-6w26"/>
  </entry>
</feed>
