CVE-2026-24332 Discord CVE debrief

Who should care

Defenders responsible for Discord deployments and user security should assess the potential impact of this vulnerability on their organization's users. This includes verifying the presence of the vulnerability, evaluating its implications for user privacy and security, and implementing appropriate measures to mitigate potential risks. Security teams should prioritize this vulnerability based on its potential to compromise user information and its medium-se

Why it matters

CVE-2026-24332 is a medium-severity vulnerability in Discord's WebSocket API service that allows gathering information about whether a user's client state is Invisible. Defenders should prioritize verifying the presence of this vulnerability in their Discord deployments and assess the potential impact on their organization's users.

• Defenders need to verify the presence of this vulnerability in their Discord deployments
• Assess the potential impact on the organization's users
• Monitor for potential exploitation attempts

Technical summary

The vulnerability allows gathering information about whether a user's client state is Invisible (and not actually offline) because the response to a WebSocket API request includes the user in the presences array (with 'status': 'offline'), whereas offline users are omitted from the presences array. This inconsistency between the API response and the UI description of Invisible as 'You will appear offline' can be used to infer a user's status, potentially impacting user privacy and security assessments. The issue highlights the importance of consistent behavior across API and UI representations of user status.

Defensive priority

Defenders should prioritize verifying the presence of this vulnerability in their Discord deployments and assess the potential impact on their organization's users.

Recommended defensive actions

• Verify the presence of this vulnerability in Discord deployments
• Assess the potential impact on the organization's users
• Monitor for potential exploitation attempts
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is described in the CVE record and NVD vulnerability detail page. A third-party report suggests that this was remediated later in 2026. The CVE record was published on 2026-01-22T08:16:00.857Z and has not been modified since then. Evidence is limited to public CVE and NVD descriptions, with no additional claims of affected scope or exploit detail.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.