Loading vulnerability…
Discord through 2026-01-16 leaks whether a user is set to Invisible (i.e., appears offline in the UI) via a behavioral discrepancy in a WebSocket API response. When querying presence information, the response includes Invisible users in the presences array with "status": "offline", whereas truly offline users are omitted from the presences array. This allows an observer to infer that a user is Invisible rather than actually offline, contradicting the UI expectation that Invisible users "will appear offline."
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
presences array (present with status: offline vs omitted). This enables inference of client state and potentially user activity patterns (e.g., that the user is online but attempting to conceal it).If you can’t patch tonight, do this now.
Patch, then assume compromise.
presences similarly to offline users, or otherwise ensure consistent response semantics) once a vendor fix is available.No valid public exploits. Mallory filtered out 2 candidates as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.