Signal calls can stay live after hang-up (RingRTC CVE-2026-113380)

## summary

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; a conceptual PoC is public, no known exploitation.

severity: CVSS 4.0 9.3 (MITRE CNA); conceptual public PoC; no known exploitation, not in CISA KEV

## cve ids[1]

## timeline[3]

1. Oct 22, 2026

   No known exploitation; CISA has not added it to KEV and NVD lists it as awaiting analysis.

   source
2. Oct 21, 2026

   Researcher Imahian's write-up and conceptual PoC circulate; press coverage begins.

   source
3. Oct 20, 2026

   CVE-2026-113380 published by MITRE (CVSS 4.0 9.3); fix is RingRTC 2.72.0.

   source

## advisories[2]

• CVE-2026-113380MITRE · Oct 20, 2026
• RingRTC fix commitSignal · Oct 20, 2026

## news & write-ups[2]

• Signal bug could keep your mic - and camera - on after hangupThe Register · Oct 21, 2026
• Signal flaw could expose audio and video even after users hang upHelp Net Security · Oct 22, 2026

## posts[2]

T

tsn_hub

@tsnmediahub

📵 Update Signal. A critical flaw in its RingRTC calling library could stop a call ending when you hang up, leaving audio and perhaps video running, per its CVE record. RingRTC 2.72.0 fixes it. There's no report of exploitation. Source: CVE-2026-113380 record

CN

Cybersecurity News Everyday

@TweetThreatNews

CVE-2026-113380 affects RingRTC versions before 2.72.0 and could let a call participant keep hearing audio after hang-up. No in-the-wild exploitation is known; users are advised to update Signal.