Quick answers
- Is CVE-2026-59726 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59726 being exploited in the wild.
- How severe is CVE-2026-59726?
- Critical severity, with a CVSS score of 10, published 9 July 2026.
- Which products and versions are affected?
- Ruvnet Ruflo < 3.16.3.
- Is there a fix for CVE-2026-59726?
- A patch was published on 2026-07-01: Fixes merged and version 3.16.3 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-59726 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-59726?
- Check whether you run Ruvnet Ruflo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Ruflo's default docker-compose deployment prior to 3.16.3 bound the MCP bridge and MongoDB services to all interfaces (0.0.0.0) without requiring authentication. This allowed unauthenticated network attackers to access the POST /mcp and POST /mcp/:group endpoints. By invoking the terminal_execute tool through these endpoints, an attacker could achieve remote code execution (RCE) within the bridge container. This access enabled the theft of provider API keys from environment variables, shell access, and the ability to poison AgentDB learning-store patterns. The fix in version 3.16.3 defaults service bindings to loopback (127.0.0.1), implements mandatory bearer token authentication for public exposure, and adds a server-side gate for terminal execution tools.
Affected products
- ruvnet Ruflo < 3.16.3
Timeline
- 2026-06-30: other: Maintainer decision on remediation strategy
- 2026-07-01: patched: Fixes merged and version 3.16.3 released
- 2026-07-09: disclosed: CVE-2026-59726 published