CVE-2026-71424 is an information exposure vulnerability in Onyx affecting versions prior to 3.1.10, 3.2.14, and 4.0.0. The flaw is present in the MCP server API handling for the GET /api/mcp/servers and GET /api/mcp/servers/persona/{persona_id} endpoints. Per-user OAuth tokens and related client information are written by OnyxTokenStorage.set_tokens and OnyxTokenStorage.set_client_info into a shared administrative MCPConnectionConfig record. That shared record is later transformed for API output by _db_mcp_server_to_api_mcp_server, which returns the stored authentication template headers to users with BASIC_ACCESS privileges. As a result, one user can receive another user's OAuth Authorization header through normal API responses, causing cross-user disclosure of bearer credentials and associated authorization context.
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.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.