// Güvenlik

A critical vulnerability in Signal can leave the microphone on even after a call ends

A bug in versions of Signal's calling library RingRTC before 2.72.0 can prevent the hang-up command from being processed if the other party fills the event queue. The audio stream may continue even when the user thinks they have ended the call.

A bug has emerged in the RingRTC library that powers Signal’s voice and video calls, affecting versions before 2.72.0. The issue, recorded as CVE-2026-113380, can cause a user’s hang-up request to go unprocessed if the queue is filled with events sent by the other party during a call. The NVD entry describes the impact as the call’s audio and, if applicable, video stream not closing. The CVSS 4.0 score is 9.3.

Why the hang-up command isn’t processed

In RingRTC, a call runs through an event queue called a finite state machine (FSM). Hang-up is also handled as an ordinary event added to this queue; it has no priority path. Events coming from the other side are not rate-limited.

As a result, when the queue is filled with events sent back-to-back during a call, the user’s “hang up” action waits at the end of the queue and may remain unprocessed. The result is that even though the call appears to have ended on screen, the audio stream continues to flow to the other party. The bug is classified under the failure to handle exceptional conditions (CWE-754) category.

Which versions are affected

The vulnerability exists in all RingRTC versions before 2.72.0. Signal clients that include this library, namely the Android, iOS, and desktop apps, may be affected until a version carrying the fixed library is released. The fix record in Signal’s own repository includes changes that ensure calls “fully terminate in edge cases.”

Fix and what to do

Signal limited the event queue and defined a maximum time for termination in RingRTC 2.72.0. In the changes, each event channel is limited to 256 events, the system waits at most 5 seconds for the event stream to quiet down during hang-up, and then the call is terminated anyway. This way, the call closes even if the queue is full.

The only thing users need to do is update the Signal app from the app store. Because the library is bundled inside the app, no separate patch is installed. If you had a sensitive conversation, it’s also a good idea to check that the call indicator disappears after you hang up.

At the moment, there is no evidence that this vulnerability is being actively exploited. However, because the privacy impact of the bug is that audio and video streams continue without the user’s knowledge, you shouldn’t delay updating.

Source: NVD · Signal RingRTC fix record

// JOIN THE CONVERSATION

Share your experience

Bir sorunun, farklı bir çözümün veya eklemek istediğin bir notun var mı? Giriş yapmadan da yazabilirsin.

// KEEP READING

One more note.

All posts ↗︎