Directory / Langflow
Langflow
The docs are blunt: Langflow runs arbitrary code with full access to the host filesystem and network, and provides no isolation between users. Component API keys are encrypted at rest.
Lock this down first
Run Langflow in an isolated container, block custom component execution if flows could run untrusted code, and set a non-default LANGFLOW_SECRET_KEY.
Scorecard
| Criterion | Rating | Notes |
|---|---|---|
| Permission granularity | 0/3 | Access controls are designed for usability, not security enforcement. Code has full access to the backend process. |
| Human approval gates | Unverified | Not confirmed in the docs we checked. |
| Sandboxing | 0/3 | No isolation. Docs say to use infrastructure-level isolation such as containers. |
| Secrets handling | 2/3 | Component API keys can be stored as encrypted global variables, encrypted with LANGFLOW_SECRET_KEY. |
| Audit logs | Unverified | Not confirmed in the docs we checked. |
| Kill switch / interrupt | Unverified | Not confirmed in the docs we checked. |
| Network egress control | 0/3 | Langflow does not restrict network access. Network isolation is left to your infrastructure. |
Sources
Vendor? Request a correction. We review corrections within 7 days.
