Noma Labs · July 29, 2026

RufRoot: unauthenticated Ruflo MCP bridge enabled RCE and memory poisoning

Why it matters

Before Ruflo 3.16.3, its default Docker Compose deployment bound the MCP bridge to all interfaces without authentication. A reachable attacker could invoke the terminal tool, read model-provider keys and conversations, spawn agents, and poison persistent AgentDB patterns. Noma Labs verified the chain; the patch adds loopback binding, bearer authentication for public exposure, an opt-in terminal tool, authenticated MongoDB, tighter CORS and container defaults, and regression tests.

My takeaway: Upgrade to Ruflo 3.16.3 or later and treat exposed instances as compromised: close ports 3001 and 27017, rotate provider secrets, inspect AgentDB and MongoDB, and rebuild from trusted images. For every MCP server, require authentication and per-tool authorization, keep dangerous tools off by default, restrict network reachability, audit memory writes, and regression-test secure deployment defaults.
Keep exploring

More curated notes connected through Agent Security and AI Red Teaming.

OpenAI News · framework

OpenAI’s Frontier Governance Framework

OpenAI's 22-page Frontier Governance Framework maps its frontier-model processes to California's Transparency in Frontier AI Act and the EU AI Act's general-purpose AI code. It documents lifecycle risk assessment, cyber-offense and other risk tiers, mitigation and residual-risk decisions, critical-incident handling, security risk management, model reporting, external review, responsibility allocation, and change control.

OpenAI News · framework

Cybersecurity in the Intelligence Age

OpenAI proposes a five-pillar strategy for AI-enabled cyber defense: tiered access for trusted defenders, faster government-industry coordination, stronger protection of frontier models and infrastructure, risk-scaled deployment monitoring, and broader defensive support for individuals and small organizations.

OWASP GenAI Security Project · guide

OWASP Top 10 for Agentic Applications for 2026

OWASP's community guide organizes agentic-system risk into ten categories, including goal hijacking, tool misuse, identity and privilege abuse, memory poisoning, insecure inter-agent communication, cascading failures, and rogue-agent behavior. It provides a shared taxonomy and mitigation starting point rather than a certification checklist or evidence that a deployed system is secure.