CVE-2021-36782 is a cleartext storage of sensitive information vulnerability in SUSE Rancher affecting versions prior to 2.5.16 and 2.6.7. Rancher API objects and cluster.management.cattle.io resources stored sensitive credentials in plaintext, allowing authenticated users with sufficient read access—such as Cluster Owners, Cluster Members, Project Owners, Project Members, and User Base roles—to retrieve secrets through the Kubernetes API or Rancher API endpoints. Exposed data could include passwords, API keys, and Rancher service account tokens.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit auxiliary module targeting Rancher (up to versions 2.5.15 and 2.6.6) affected by CVE-2021-36782. The module exploits an information disclosure vulnerability where Rancher stores sensitive credentials (passwords, API keys, service account tokens) in plaintext within Kubernetes objects accessible via the Rancher API. The exploit requires valid credentials for a Rancher user with API access. Upon successful authentication, it queries multiple API endpoints to enumerate and extract sensitive fields from the returned JSON data. The module is written in Ruby and leverages the Metasploit framework's HTTP client capabilities. The structure is typical for a Metasploit module, with clear separation of initialization, authentication, and exploitation logic. The main exploit capability is authenticated extraction of plaintext secrets from Rancher-managed Kubernetes objects via the API.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.