— Ingenious AI security check.
If you run Langflow — the visual AI-agent builder — check your version against the CVE-2026-105740 advisory now. AI tooling is a fresh, high-value target: exposed instances get scanned within hours of disclosure. Paste your version into the checker above for an instant verdict, then patch.
Any logged-in Langflow user can run OS commands on your server by adding an MCP server with the stdio transport — the command field is passed straight to the shell with no validation. Previdian's honeypots have logged 1,423 exploit attempts from 27 attacker IPs since September 19, spiking to 333 attempts in a single day on October 11 — and they're still coming. This free CVE check tool tells you if you're at risk. No signup, nothing installed.
/api/v1/auto_login. If auto-login is disabled (as it should be), they fall back to common username/password combos — and it works often enough to keep the campaign running.LANGFLOW_SECRET_KEY, LANGFLOW_SUPERUSER_PASSWORD), exfiltrated to 146.70.211[.]112:18764. Other payloads run Docker commands to reach the host filesystem and read /etc/passwd.192.255.229[.]92 — heavily involved in the env-var theft and also seen brute-forcing and hitting other Langflow/Flowise flaws — plus the exfil host 146.70.211[.]112.LANGFLOW_AUTO_LOGIN=false, enforce strong unique passwords, block both IPs at your firewall, and grep your logs for /api/v1/auto_login hits — any 200 response there means someone walked straight in.Check your Langflow version — on the host running Langflow:
pip show langflow | grep -i version
Docker users: check the image tag you deployed (e.g. langflowai/langflow:1.8.x).
Audit your MCP servers — list every configured MCP server and look for stdio-transport entries you didn't authorize:
curl -s -H "Authorization: Bearer $LF_API_KEY" \
http://localhost:7860/api/v2/mcp/servers | python3 -m json.tool | grep -A3 stdio
Any stdio entry with a command you don't recognize was potentially planted — the payload executes when the server list is fetched.
Check for signs of past compromise — look for unexpected MCP server registrations in your logs:
grep "POST /api/v2/mcp/servers" /var/log/langflow/*.log | grep -v "your-admin-user"
Also hunt for new processes, cron entries, or outbound connections you can't explain — RCE gives the attacker the whole host, not just Langflow.
This page checked one CVE. Rogue-Agent Defense monitors your AI agents for prompt injection, data exfiltration, and anomalous tool use — the things an exploited agent does next.
Drop a live version-checker into your blog, docs, or forum post — three lines of HTML.
Get the embed codeCheck your Langflow version: anything below 1.9.0 is vulnerable to authenticated remote code execution via the MCP stdio transport. Then list your configured MCP servers — any stdio-transport entry added by a user you don't fully trust deserves a review. The free 30-second self-test on this page walks through the exact checks.
No. Any authenticated Langflow user — even a low-privilege one — can add a malicious MCP server with the stdio transport and get full OS command execution on the host. That is what makes this flaw critical: the privilege boundary that should protect the server does not hold.
Upgrade to the latest release (1.10.3 or newer; 1.9.0 is the minimum). Audit every MCP server entry for commands you did not authorize, check server logs for unexpected POSTs to /api/v2/mcp/servers, and rotate all secrets stored on the host — API keys, database credentials, model tokens — because RCE means they may have been read.
A CVE checker is a free tool that tells you whether your software is affected by a published CVE — a publicly known cybersecurity vulnerability. It compares your version or configuration against the official advisory and gives you a patched, vulnerable, or unknown verdict in about 30 seconds.
Find your exact version number, then compare it against the vendor's security advisory or the NVD entry for the CVE. The fastest way is a CVE checker built for that product: paste your version and get an instant verdict against the published version tables.
You are affected when you run a vulnerable version and the vulnerable component is reachable or enabled — for example, open sign-ups, an exposed management port, or a vulnerable app installed. A CVE checker gives you the version verdict in seconds; the advisory's conditions tell you whether that verdict means real exposure.