Security

Ruflo closes critical security vulnerability in AI agents

3 min read

TL;DR Too Long; Didn’t read

Ruflo, an open-source platform for controlling multiple AI agents, had an unprotected network interface until version 3.16.3. A single HTTP call without credentials was sufficient to open foreign server shells, steal access keys for language models, and manipulate the permanent agent memory. Security researcher Eli Ainhorn reported the finding on June 30, 2026, and the provider responded within a day.

A server rack with a blue Ruflo wave sticker stands open with no door, while a robotic hand reaches out and grabs several glowing key cards Image generated with GPT Image 2

Key takeaways

  • The vulnerability is identified as CVE-2026-59726 and affects all Ruflo releases prior to version 3.16.3.
  • The cause was an open API that made 233 functions accessible without a password or token.
  • Attackers gained shell access via terminal command and could read access credentials for language models.
  • The database containing stored conversations and learning patterns of the agents was also accessible without protection.
  • Ruflo founder Reuven Cohen released the patch within 24 hours of the confidential report.
  • Operators must additionally change their access keys and check the agent storage in addition to the update.

The security company Noma Security has uncovered a critical vulnerability in the open-source AI agent platform Ruflo, with a CVSS score of 9.8 out of 10. Through a single unauthenticated network request, attackers could remotely control foreign installations, steal access keys, and manipulate the persistent memory of the AI agents. The provider closed the gap with version 3.16.3; all previous releases were affected.

Open Interface Exposes 233 Tools Without Protection

Ruflo is open-source software that allows companies and developers to coordinate multiple AI agents to work together – for example, in conjunction with Anthropic’s Claude Code or OpenAI’s Codex. The project has around 67,000 stars on GitHub and more than ten million downloads – numbers that are not independently verified. The core of the architecture is a so-called MCP bridge, a server that provides tools such as terminal commands, database access, or storage functions for the agents.

That’s where the problem lay: In the default configuration of the Docker setup, the bridge bound network port 3001 to all interfaces and provided 233 tools without any authentication. A single unauthenticated HTTP POST request to the endpoint “/mcp” was sufficient to invoke any function of the bridge. According to the official security advisory on GitHub, attackers gained shell access as the system user “node” within the bridge container – enough to execute arbitrary commands.

Attackers Gain Access Keys and Persistent Memory

From the shell, attackers could read all environment variables of the container, including the access keys for the connected language model providers. With these keys, they could make their own requests at the expense of the affected parties or launch complete swarms of agents under foreign control. The associated MongoDB database, where Ruflo stores conversation logs and learning patterns, was also accessible by default without a password.

Particularly critical: through the database, the so-called AgentDB pattern store could be manipulated, where Ruflo stores recurring behavior patterns for its agents. Anyone who deliberately places poisoned entries here can permanently change the behavior of the AI agents for all users of an installation – for example, by classifying malicious code as trustworthy. In a demonstration, the research team showed a complete attack chain from the first request to permanent backdoor access, including the elimination of traces.

Ruflo Patches Within a Day, Operators Must Act Themselves

Security researcher Eli Ainhorn responsibly reported the vulnerability to Ruflo founder Reuven Cohen on June 30, 2026. According to the release notes for version 3.16.3, the project released a patch on July 1, 2026. The new version now binds the MCP bridge by default only to the local address 127.0.0.1, requires an access token for public access, and disables the terminal function unless explicitly activated. The database has also required a password since then.

Ruflo is free, open-source software that is uniformly available for download worldwide via GitHub and the npm package manager – there is no restriction for Germany or the EU. Anyone running an older version should immediately update to 3.16.3 or newer, secure ports 3001 and 27017 via firewall, replace all keys for connected AI providers, and check the AgentDB pattern store for suspicious entries.

It remains open how many of the approximately one million active Ruflo installations, according to the project, still operate the open default configuration unchanged – unpatched servers remain discoverable through automated scans even weeks after the vulnerability is made public. The case is also part of a series of security incidents surrounding autonomous AI agent frameworks, as demonstrated recently by the misuse of the open-source tool Hermes Agent for automated attacks on more than 460 systems. The more companies deploy agents with extensive tool rights, the more the risk shifts from the quality of individual models to the security of the surrounding infrastructure.

Frequently asked questions

Is Ruflo safe to use after the update?

Yes, as long as it is updated to version 3.16.3 or newer and the recommended measures such as firewall rules and key changes are implemented. Instances that were openly operated before the patch should also be checked for compromise.

What does Ruflo cost?

Ruflo is free open-source software with no licensing fees; costs may arise only for the server infrastructure used and the connected AI models themselves.

Are only self-hosters affected?

The standard configuration of self-hosted Docker installations was affected; there is no information available about a separate, centrally operated cloud service by Ruflo.

How can I check if my installation has been attacked?

Ruflo recommends in the release notes to examine the AgentDB pattern storage for unknown entries and to check the logs of the MCP bridge for unusual requests to the endpoint '/mcp'.

Are there similar vulnerabilities in other agent frameworks?

Comparable issues with open, unauthenticated tool interfaces have already been documented in other AI agent systems; a uniform security standard for the underlying Model Context Protocol does not yet exist.

Sources (4)
  1. Noma Security: RufRoot – The MCP Bridge Vulnerability That Turns Agents Into Rogue Admins (CVE-2026-59726)
  2. GitHub Security Advisory GHSA-c4hm-4h84-2cf3 (ruvnet/ruflo)
  3. GitHub: Ruflo Release v3.16.3 – Security release
  4. The Hacker News: Ruflo MCP Flaw Lets Unauthenticated Attackers Run Commands and Poison AI Memory

Your AI update for the work week

Once a week, the most important AI news – plus one practical tip to try right away. No spam, unsubscribe anytime.

← Back to the blog