Loading vulnerability…
MindsDB versions prior to 25.9.1.1 contain a path traversal vulnerability in the multipart file-upload functionality. The upload operation writes attacker-controlled content using the supplied filename before filename sanitization and file-saving logic is applied. An authenticated attacker can use traversal sequences to write arbitrary content outside the intended upload directory, potentially overwriting server-side executable or scripted components and obtaining remote code execution.
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 (2 hidden).
Repository contains a MindsDB path traversal-to-RCE proof-of-concept for CVE-2026-27483, plus a Nuclei template for detection/verification. Structure and purpose: - README.md: Describes the vulnerability and PoC workflow: query status, optionally authenticate, abuse PUT /api/files/ to traverse and overwrite pip/__init__.py, then trigger execution via handler installation. - cve-2026-27483.py: Standalone Python exploit. It fingerprints the target via GET /api/status, aborts if version >= 25.9.1.1 (patched), optionally logs in via POST /api/login to obtain a Bearer token, then performs a multipart PUT to /api/files/{randomname} with a crafted filename of '../../../../../../venv/lib/python3.10/site-packages/pip/__init__.py' to achieve arbitrary file write. The written content is a Python reverse shell that connects back to attacker-supplied LHOST:LPORT and spawns /bin/sh. Finally, it triggers execution by POSTing to /api/handlers/anomaly_detection/install. - cve-2026-27483.yaml: Nuclei template marked intrusive. It fingerprints version/auth via /api/status, optionally obtains a token via /api/login, uploads a traversal file overwrite to pip/__init__.py containing an interactsh HTTP callback, triggers via /api/handlers/anomaly_detection/install (expects a 500 with 'Failed to install dependencies'), and verifies via interactsh DNS interaction. Main exploit capabilities: - Network-based exploitation over HTTP. - Works in unauthenticated mode when MindsDB http_auth_enabled is false; supports authenticated mode via Bearer token. - Arbitrary file write through path traversal in multipart upload filename. - RCE achieved by overwriting a Python module (pip/__init__.py) and triggering a code path (handler install) that causes execution/import side effects; PoC yields a reverse shell.
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.
11 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.