Loading vulnerability…
CVE-2026-57219 is a sensitive information disclosure vulnerability in RabbitMQ, a messaging and streaming broker. In affected versions, the obsolete management HTTP API endpoint GET /api/auth can return the configured OAuth 2 client secret to unauthenticated callers. The issue occurs on installations where the management plugin is enabled and the RabbitMQ configuration includes management.oauth_client_secret as part of the OAuth 2 setup. As a result, a remote attacker can retrieve the OAuth 2 client secret without authentication. The vulnerability affects RabbitMQ versions prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6.
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.
3 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.