Discord's encrypted-call flaw needed signalling control. The fix shipped five weeks before disclosure

Encryption depends on knowing who is in the group

Discord's libdave library is part of its end-to-end encrypted media system. CVE-2026-104480, published on 2 October, says versions before 1.2.0 did not reject an MLS Welcome message if the resulting group roster contained a participant the client did not recognise. An attacker able to change signalling messages could cause an affected client to accept an unauthorised member into an audio or video session.

This is a membership-validation problem. It does not mean the media encryption itself was mathematically broken. If the wrong person is admitted as a group member, sound encryption can faithfully protect media for the wrong set of people. That distinction is the useful lesson of this disclosure.

The trust decision described by the CVE record.

Step	Required condition	Potential result
Signalling	Attacker controls the DAVE signalling path, such as the voice gateway or an equivalent position	Welcome message can be added, altered or withheld
Roster validation	Affected libdave build before 1.2.0 accepts an unrecognised participant	Client accepts the wrong membership
Media	Unauthorised member is in the encrypted session	Audio/video confidentiality and integrity can be affected

Where the Voice Gateway sits in the trust decision

DAVE uses Message Layer Security (MLS) to manage who belongs to an encrypted audio or video group. Discord's Voice Gateway carries the signalling that clients use to set up and update that group, while the SFU forwards encrypted media frames. A Welcome message lets a participant join an MLS group. Before accepting it, a client needs to match the resulting cryptographic membership to the participants it expects.

The CVE says libdave before 1.2.0 failed that last check when a Welcome led to an unrecognised group member. The attacker condition is substantial: control of the DAVE signalling path, such as the voice gateway or equivalent ability to alter, add or withhold messages. It is not enough simply to join a normal call. If the condition and vulnerable code coincide, the wrong member can become part of the encrypted group and gain access to media intended for that group. The CVE describes a possible confidentiality and integrity impact, not a confirmed recording of calls.

The mechanism crosses a membership boundary, not the media cipher.

Layer	Normal role	Failure or fix
Voice Gateway signalling	Delivers MLS messages	Attacker-controlled signalling is the prerequisite
MLS Welcome validation	Checks membership against expected participants	Pre-1.2.0 missed unrecognised member; 1.2.0 rejects
Encrypted media	Protects frames for accepted group	Wrong accepted member can defeat intended audience

What call participants can independently check

DAVE documents a Voice Privacy Code that group members may compare through an independent channel. This can help participants assess whether they share the same encrypted conversation, but the public CVE does not show that checking the code would always detect or prevent this particular roster bug. The engineering fix is to ship libdave 1.2.0 or later and validate every membership transition. Incident claims still need evidence that an attacker controlled signalling and that affected clients were in the call.

The patch preceded the CVE by more than a month

The corrective commit restores stricter validation of the Welcome state. The libdave v1.2.0 release is dated 26 August 2026. The CVE record appeared 2 October 2026, roughly five weeks later. The elapsed time between fix and disclosure is visible; whether vulnerable clients remained in use during that period is not.

The record does not say an attacker exploited this flaw, identify affected calls, or state which current Discord clients had an older library. A headline claiming all Discord calls were exposed would go beyond the evidence. Third-party applications embedding libdave should check their actual bundled version, not only the upstream release date.

What implementers should take from it