Loading vulnerability…
Vanus versions 0.8.0 through 0.9.0 contain a hardcoded default administrative token that allows remote attackers without legitimate credentials to obtain cluster-admin access. Supplying the fixed Bearer token to the gateway gRPC proxy port grants access to administrative operations for namespaces, eventbuses, users, tokens, and role bindings, as well as event reading and publishing.
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.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A hardcoded administrator Bearer token in Vanus versions 0.8.0 through 0.9.0 allows otherwise unauthenticated remote attackers to obtain cluster-admin access through the gateway gRPC proxy port. Attackers can manage namespaces, eventbuses, users, tokens, and role bindings, as well as read or publish events.
A critical default-credentials vulnerability affecting Vanus versions 0.8.0 through 0.9.0. Remote attackers can submit a fixed Bearer token to the gateway gRPC proxy port to obtain cluster-admin access, manage namespaces, eventbuses, users, tokens, and role bindings, and read or publish events. The reference reports CVSS scores of 9.8 (3.1) and 9.3 (4.0). It recommends updating to a patched version, removing or changing default credentials, restricting gateway access, and monitoring for unauthorized access; no specific fixed version is identified.
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.