Menu

RAGFlow private agents were not private through the OpenAI-compatible endpoint
📰

RAGFlow private agents were not private through the OpenAI-compatible endpoint

DEV Community: cybersecurity·facilishz·3 days ago
#UbgykF2s
#devtocybersecurity#devto#dev#agent#ragflow
Reading 0:00
15s threshold

RAGFlow private agents were not private through the OpenAI-compatible endpoint

A private agent setting should follow the agent into every execution interface. RAGFlow had a path where it did not. The October 5, 2026 advisory GHSA-c6q8-23rp-32cv describes an authenticated user who can run another user's Only me agent by knowing its UUID and sending it to POST /api/v1/agents/chat/completions with "openai-compatible": true .

The endpoint matters because it imitates an OpenAI-compatible completion API. A client that uses that interface may treat the agent ID as a model identifier. The normal agent UI may enforce a permission check, while the compatibility route reaches the same execution engine through a different request path. The advisory states that the private-agent check was skipped and that the caller could read the output.

An agent can contain prompts, retrieval settings, connected data sources, and tools.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.