How do I secure Flowise?

Enable Flowise auth: set FLOWISE_USERNAME and FLOWISE_PASSWORD on the service and restart. There is no auth by default.

EXPOSURE Flowise
SEVERITY CRITICAL
PROBE GET :3000/api/v1/ping

CRITICAL

Is your Flowise exposed?

Q: How many Flowise instances are exposed?

3,390 Flowise instances are reachable in the Shodan index (source: Shodan count · `http.html:"Flowise - Build AI Agents, Visually"`, 2026-08); that is a fingerprint match, not a verified zero-auth count.

Public chatflows/agentflows are callable; builder holds credentials and model keys.

Scan a host you own → Fix card Census

Why it matters

Your Flowise agent builder is public. Chatflows and agentflows, stored credentials, and model API keys sit behind it. Flowise also whitelists /api/v1/public-chatflows and /api/v1/prediction/ — strangers can discover public flows and run your agents on your bill without logging in.

How common is it?

3,390 Flowise instances are reachable in the Shodan index. Fingerprint match, not a verified zero-auth count · src: Shodan count · `http.html:"Flowise - Build AI Agents, Visually"` · 2026-08

Counts are population-level, from third-party indexes and my own honeypots. I never scan the internet and this page makes no claim about any specific host.

Fix it

The full walkthrough lives on the fix card, kept current in one place:

Full fix card: flowise-exposed →