Skip to content
Signal Fixes Critical Flaw Allowing Eavesdropping After Call Hangup

Signal Fixes Critical Flaw Allowing Eavesdropping After Call Hangup

First seen 21 Oct 2026, 13:17 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •October 22, 2026 at 13:13 UTC
  • •CVE-2026-113380 has a CVSS score of 9.3, indicating critical severity.
  • •The vulnerability allows eavesdropping by preventing proper call termination.
  • •Users should update to RingRTC version 2.72.0 or later to mitigate the risk.

Signal has patched a critical vulnerability in its RingRTC calling library, tracked as CVE-2026-113380, which could allow a malicious participant to continue hearing audio after a call has ended. The flaw affects versions prior to 2.72.0 and has a CVSS score of 9.3. It involves the library's finite state machine queue, which can be overwhelmed, preventing proper call termination. While the vulnerability does not compromise encryption, it poses a significant privacy risk. No known exploitation has been reported in the wild. Users are advised to update to the latest version of the Signal app to mitigate this risk. The patch was included in RingRTC version 2.72.0, released on September 4, 2026.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Timeline

2026-09-04
Patch released for RingRTC
Signal released version 2.72.0, fixing the critical flaw CVE-2026-113380 in its calling library.
Cyberinsider
2026-10-20
CVE-2026-113380 published
The vulnerability was disclosed, highlighting the risk of continued audio transmission after hangup.
Cyberinsider
2026-10-21
Malwarebytes reports on vulnerability
Malwarebytes published an article detailing the implications of the Signal bug and urging users to update.
Malwarebytes

More articles in this cluster (7)

Following this threat?

Track Signal and CVE-2026-113380 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

Which versions of Signal are affected?
Any version of Signal using RingRTC prior to 2.72.0 is affected by this vulnerability.
Is this vulnerability being actively exploited?
No known exploitation has been reported in the wild as of now.
What should users do to protect themselves?
Users should update their Signal app to the latest version to ensure they are protected from this vulnerability.