RufRoot is an unauthenticated remote code execution vulnerability in Ruflo versions before 3.16.3 when deployed using the previous default Docker Compose configuration. The MCP Bridge was network-accessible by default and exposed tool-invocation functionality without authentication. An unauthenticated attacker could invoke the terminal execution tool to run commands as the bridge container's node user, access provider credentials, retrieve stored conversations, and modify AgentDB learning-store patterns.
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 valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
44 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical unauthenticated-exposure vulnerability in Ruflo's MCP bridge. Default configuration exposes the bridge on all network interfaces without authentication or IP restrictions, allowing access to agent tools, API keys, conversation logs, and effective administrator-level agent control.
An unauthenticated remote code execution vulnerability in ruflo MCP Bridge, reportedly reachable via terminal functionality.
A critical unauthenticated remote command execution vulnerability in Ruflo's MCP bridge caused by exposing the POST /mcp endpoint without authentication in default self-hosted docker-compose deployments.
A maximum-severity unauthenticated remote code execution vulnerability in the Ruflo open-source AI agent platform that can expose API keys, stored conversations, and enable persistent AI memory tampering ('memory poisoning') even after patching.
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.