<?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-22T11:36:27.366071+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-74758</id>
    <title>fkie_cve-2026-74758</title>
    <updated>2026-10-22T11:36:27.385987+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>A heap use-after-free in the RTMP protocol component of Apache bRPC (versions &lt; 1.18.0) allows a remote attacker to crash a bRPC RTMP server by sending a crafted Abort control message. No authentication or application-level request is required.</p>
<p>Root Cause:
When an RTMP Abort control message names the chunk stream that is currently being parsed (the chunk stream carrying the message itself), RtmpChunkStream::OnAbortMessage calls RtmpContext::ClearChunkStream, which deletes the RtmpChunkStream while its Feed() is still running. After the message handler returns, Feed() continues to access members of the deleted object, resulting in a heap-use-after-free.</p>
<p>Affected Scenarios:
bRPC servers that enable RTMP support (ServerOptions.rtmp_service set) and accept connections from untrusted networks.</p>
<p>How to Fix:
1. Upgrade bRPC to version 1.18.0, which fixes this issue.
2. Apply this patch:  https://github.com/apache/brpc/pull/3452</p>
<p>The fix skips clearing the chunk stream when the Abort message targets the chunk stream that is currently being parsed.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-74758"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-jhf7-xcw3-gmv5</id>
    <title>GHSA-jhf7-xcw3-gmv5</title>
    <updated>2026-10-22T11:36:27.386068+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>A heap use-after-free in the RTMP protocol component of Apache bRPC (versions &lt; 1.18.0) allows a remote attacker to crash a bRPC RTMP server by sending a crafted Abort control message. No authentication or application-level request is required.</p>
<p>Root Cause:
When an RTMP Abort control message names the chunk stream that is currently being parsed (the chunk stream carrying the message itself), RtmpChunkStream::OnAbortMessage calls RtmpContext::ClearChunkStream, which deletes the RtmpChunkStream while its Feed() is still running. After the message handler returns, Feed() continues to access members of the deleted object, resulting in a heap-use-after-free.</p>
<p>Affected Scenarios:
bRPC servers that enable RTMP support (ServerOptions.rtmp_service set) and accept connections from untrusted networks.</p>
<p>How to Fix:
1. Upgrade bRPC to version 1.18.0, which fixes this issue.
2. Apply this patch:  https://github.com/apache/brpc/pull/3452</p>
<p>The fix skips clearing the chunk stream when the Abort message targets the chunk stream that is currently being parsed.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-jhf7-xcw3-gmv5"/>
  </entry>
</feed>
