<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>pwn.watch: Signal incident updates</title>
  <link>https://pwn.watch/t/signal</link>
  <description>Live security incidents worldwide: CVEs, patch status, fixed versions, advisories and the posts that broke them.</description>
  <language>en</language>
  <lastBuildDate>Thu, 22 Oct 2026 16:00:43 GMT</lastBuildDate>
  <atom:link href="https://pwn.watch/t/signal/feed.xml" rel="self" type="application/rss+xml" />
  <item>
    <title>[critical] Signal calls can stay live after hang-up (RingRTC CVE-2026-113380)</title>
    <link>https://pwn.watch/i/signal-ringrtc-cve-2026-113380</link>
    <guid isPermaLink="true">https://pwn.watch/i/signal-ringrtc-cve-2026-113380</guid>
    <pubDate>Thu, 22 Oct 2026 16:00:43 GMT</pubDate>
    <category>critical</category>
    <description>&lt;p&gt;A bug in RingRTC, the open-source library behind Signal's voice and video calls, lets the other party on a call flood the call's state-machine event queue so a local hang-up gets stuck behind the backlog, and audio (possibly video) keeps flowing to them after the victim thinks the call ended. Affects every Signal client (Android, iOS, Desktop) embedding RingRTC before 2.72.0. Fixed in RingRTC 2.72.0 (released Sep 4 2026, disclosed Oct 20); a conceptual PoC is public, no known exploitation.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; closed · &lt;strong&gt;Patch:&lt;/strong&gt; patched · &lt;strong&gt;Fixed in:&lt;/strong&gt; RingRTC 2.72.0 (update Signal on every device)&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Latest updates:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;2026-10-22: No known exploitation; CISA has not added it to KEV and NVD lists it as awaiting analysis. (&lt;a href=&quot;https://www.helpnetsecurity.com/2026/10/22/signal-ringrtc-vulnerability-cve-2026-113380/&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;li&gt;2026-10-22: SecurityWeek: the hang-up was queued behind peer events with no rate limit or priority; the fix makes call termination bypass the queue. Users should update Signal and check the call indicator after hanging up. (&lt;a href=&quot;https://www.securityweek.com/signal-vulnerability-lets-malicious-callers-block-hang-ups/&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;li&gt;2026-10-22: Closed on pwn.watch: the fix shipped Sep 4 (RingRTC 2.72.0), there is still no known exploitation and no new developments, so this is now a patch-and-move-on item. Make sure Signal is updated on every device. (&lt;a href=&quot;https://www.securityweek.com/signal-vulnerability-lets-malicious-callers-block-hang-ups/&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;CVEs:&lt;/strong&gt; CVE-2026-113380&lt;/p&gt;</description>
  </item>
</channel>
</rss>
