CVE-2026-30820: Flowise Flowise Has Authorization Bypass Vulnerability
HIGHCVE-2026-30820 is a HIGH flowise has authorization bypass vulnerability (CWE-863: Incorrect Authorization) affecting Flowise libraries in the npm ecosystem. The issue involves flowise has authorization bypass via spoofed x-request-from header. Remediation is available by upgrading affected packages to version 3.0.13.
CVE-2026-30820 at a Glance
How to Fix CVE-2026-30820
To remediate this vulnerability, upgrade all affected Flowise dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install flowise@3.0.13
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls flowise
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-30820, inspect your project dependencies using npm:
npm ls flowise
Analyze the terminal output to locate any version of Flowise in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.0.13), your application is affected.
Note: The npm ls flowise command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-863: Incorrect Authorization, where the product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. In Flowise, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-30820 Affected Flowise Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
flowise
|
npm |
< 3.0.13
|
3.0.13
|
References
Frequently Asked Questions
What is CVE-2026-30820?
Which Flowise versions are affected?
What version fixes CVE-2026-30820?
Is flowise affected?
What CWE is associated with CVE-2026-30820?
How can I check npm dependencies for CVE-2026-30820?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-wvhq-wp8g-c7vq",
"modified" : "2026-03-09T13:15:20Z",
"published" : "2026-03-06T18:48:22Z",
"aliases" : [ "CVE-2026-30820" ],
"summary" : "Flowise has Authorization Bypass via Spoofed x-request-from Header",
"details" : "### Summary\n\nFlowise trusts any HTTP client that sets the header `x-request-from: internal`, allowing an authenticated tenant session to bypass all `/api/v1/**` authorization checks. With only a browser cookie, a low-privilege tenant can invoke internal administration endpoints (API key management, credential stores, custom function execution, etc.), effectively escalating privileges.\n\n### Details\n\nThe global middleware that guards `/api/v1` routes lives in `external/Flowise/packages/server/src/index.ts:214`. After filtering out the whitelist, the logic short-circuits on the spoofable header:\n\n```javascript\nif (isWhitelisted) {\n next();\n} else if (req.headers['x-request-from'] === 'internal') {\n verifyToken(req, res, next);\n} else {\n const { isValid } = await validateAPIKey(req);\n if (!isValid) return res.status(401).json({ error: 'Unauthorized Access' });\n … // owner context stitched from API key\n}\n```\n\nBecause the middle branch blindly calls verifyToken, any tenant that already has a UI session cookie is treated as an internal client simply by adding that header. No additional permission checks are performed before `next()` executes, so every downstream router under `/api/v1` becomes reachable.\n\n### PoC\n\n1. Log into Flowise 3.0.8 and capture cookies (e.g., `curl -c /tmp/flowise_cookies.txt … /api/v1/auth/login`).\n2. Invoke an internal-only endpoint with the spoofed header:\n\n```bash\n curl -sS -b /tmp/flowise_cookies.txt \\\n -H 'Content-Type: application/json' \\\n -H 'x-request-from: internal' \\\n -X POST http://127.0.0.1:3100/api/v1/apikey \\\n -d '{\"keyName\":\"Bypass Demo\"}'\n```\n The server returns HTTP 200 and the newly created key object.\n3. Remove the header and retry:\n\n```bash\n curl -sS -b /tmp/flowise_cookies.txt \\\n -H 'Content-Type: application/json' \\\n -X POST http://127.0.0.1:3100/api/v1/apikey \\\n -d '{\"keyName\":\"Bypass Demo\"}'\n```\n This yields {\"error\":\"Unauthorized Access\"}, confirming the header alone controls access.\n\nThe same spoof grants access to other privileged routes like `/api/v1/credentials`, `/api/v1/tools`, `/api/v1/node-custom-function`, etc.\n\n### Impact\n\nThis is an authorization bypass / privilege escalation. Any authenticated tenant (even without API keys or elevated roles) can execute internal administration APIs solely from the browser, enabling actions such as minting new API keys, harvesting stored secrets, and, when combined with other flaws (e.g., Custom Function RCE), full system compromise. All self-hosted Flowise 3.0.8 deployments that rely on the default middleware are affected.",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "flowise"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "3.0.13"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 3.0.12"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-wvhq-wp8g-c7vq"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-30820"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/FlowiseAI/Flowise"
}, {
"type" : "WEB",
"url" : "https://github.com/FlowiseAI/Flowise/releases/tag/flowise%403.0.13"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-863" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-03-06T18:48:22Z",
"nvd_published_at" : "2026-03-07T05:16:26Z"
}
}