CVE-2023-37941 is a deserialization-related vulnerability in Apache Superset affecting versions 1.5.0 through 2.1.0. If an attacker obtains write access to the Superset metadata database, they can persist a specially crafted Python object in that database. When the Superset web backend later processes that object, it may result in remote code execution in the backend process context. The issue is notable because the vulnerable data path relies on the application's trust in objects stored in its internal metadata database.
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 module (modules/exploits/linux/http/apache_superset_cookie_sig_rce.rb) that exploits multiple vulnerabilities in Apache Superset (<= 2.0.0) related to insecure default Flask secret keys and improper session handling. The exploit forges a signed session cookie to impersonate an administrator, accesses the Superset database to extract credentials, and injects a malicious pickled Python payload to achieve remote code execution (RCE) on the server. The module supports cleanup by removing any artifacts (dashboard, SQL Lab tab, database mapping) created during exploitation. The exploit is weaponized, supporting customizable Python payloads via Metasploit, and targets network-accessible Superset instances. The code is written in Ruby and leverages Metasploit's HTTP client and payload framework. Key endpoints include the login page and various Superset API endpoints for dashboard and database management.
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.
2 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.