CVE-2026-24332 Discord CVE debrief

Who should care

Defenders responsible for Discord deployments, security teams, and vulnerability management teams should care about this vulnerability as it may impact user data and allow gathering information about user client states. They should prioritize verifying the presence of this vulnerability in their Discord deployments and assessing the potential impact on their organization's user data.

Why it matters

CVE-2026-24332 is a medium-severity vulnerability in Discord 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 assessing the potential impact on their organization's user data.

• Defenders need to verify the presence of this vulnerability in their Discord deployments.
• The vulnerability may allow gathering information about user client states.
• The inconsistency between the API response and UI description may lead to confusion.

Technical summary

The vulnerability exists because the response to a WebSocket API request includes the user in the presences array with a status of 'offline', even though the user is not actually offline. This behavior is inconsistent with the UI description of Invisible as 'You will appear offline.' The vulnerability 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 assessing the potential impact on their organization's user data.

Defensive priority

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

Recommended defensive actions

• Verify the presence of this vulnerability in Discord deployments
• Assess the potential impact on user data
• 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 CVE record and NVD vulnerability detail page provide information about the vulnerability. However, the scope of affected versions and remediation steps are not explicitly stated. Defenders should verify the presence of this vulnerability in their Discord deployments and assess the potential impact on their organization's user data by reviewing the official CVE record and NVD detail page. The inconsistency between the API response and UI description may lead to confusion, and defenders should prioritize verifying the presence of

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.