← fix library

FIX CARD
PRODUCT Flowise
SEVERITY CRITICAL

CRITICAL

Flowise agent builder / public chatflows exposed

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.

Fix it: 3 steps

  1. Enable Flowise auth: set FLOWISE_USERNAME and FLOWISE_PASSWORD on the service and restart. There is no auth by default.
  2. Do not mark chatflows/agentflows as public unless they are intentionally anonymous; require API keys on every prediction endpoint.
  3. If it is only for you, bind it to 127.0.0.1 or block the port: sudo ufw deny 3000. Rotate model API keys if it sat open.

Verify it’s fixed

curl -m 5 http://YOUR_SERVER_IP:3000/api/v1/public-chatflows; curl -m 5 http://YOUR_SERVER_IP:3000/api/v1/ping  # strangers should not get a flow list or an open builder

References

Not sure if your stack is exposed?

Run the free check: usually under a minute, safe read-only probes.

Scan your stack