What is the CVSS score of CVE-2026-30820?

CVE-2026-30820 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.1%.

Is there a public PoC exploit available for CVE-2026-30820?

Yes, a public proof-of-concept exploit is available for CVE-2026-30820. Prioritise patching immediately. EPSS: 0.1%.

How to fix or mitigate CVE-2026-30820?

Within 24 hours: Inventory all Flowise deployments and document current versions; isolate any instances running versions below 3.0.13 from production if possible. Within 7 days: Implement WAF rules to block requests with x-request-from: internal headers from external sources; enable detailed API logging to detect exploitation attempts. Within 30 days: Upgrade to Flowise 3.0.13 or later once available; conduct forensic review of API access logs for unauthorized activity; reset credentials for all tenant accounts as a precaution.

Flowise CVE-2026-30820

HIGH

Incorrect Authorization (CWE-863)

2026-03-07 security-advisories@github.com

GHSA-wvhq-wp8g-c7vq

Authentication Bypass AI / ML Flowise Flowiseai

8.8

CVSS 3.1 · GitHub Advisory

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Authenticate as low-privilege tenant
Delivery

Set x-request-from: internal header
Exploit

Bypass authorization checks on /api/v1/** endpoints
Execution

Access admin functions and API keys
Impact

Escalate privileges

Vulnerability Assessment

Weakness	CWE CWE-863 OWASP Top 10:2025 A01:2025 - Broken Access Control ASVS 5.0 V8 - Authorization Authorization logic validation MITRE ATT&CK 1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. Sign in to read
Exploitation Conditions	Flowise versions prior to 3.0.13 with x-request-from: internal header trust mechanism enabled. Attacker must possess valid authenticated tenant session cookie. Internal admin API endpoints (/api/v1/**) must be accessible.
Impact	CVSS 8.8 (HIGH). Attack vector: Network. Complexity: Low. Privileges required: Low. User interaction: None. Exploitation requires authentication. Public exploit/POC available.
Exploit ScenarioDerived	An attacker (requires authentication) could exploit this vulnerability to compromise the affected system.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

Privilege escalation in Flowise versions prior to 3.0.13 allows authenticated users to bypass API authorization by spoofing an internal request header, granting access to sensitive administrative functions including API key and credential management. Public exploit code exists for this vulnerability, and an attacker with valid tenant credentials can escalate to administrative privileges without additional authentication. No patch is currently available for affected deployments.

Earlier versions of this analysis (1)

v1 Mar 12, 2026 - 21:55 CVSS 8.8

RemediationAI

Fixed in version 3.0.13.. Restrict network access to the affected service where possible.

Affected Packages

npm flowise fix: 3.0.13

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in npm

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Classified as CWE-863 (Incorrect Authorization). Affects Flowise. Flowise is a drag & drop user interface to build a customized large language model flow. Prior to version 3.0.13, Flowise 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 privilege. This issue has b

Know when Flowise gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 8.8 HIGH

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Patch released

Mar 31, 2026 - 21:13 nvd

Patch available

PoC Detected

Mar 11, 2026 - 13:46 vuln.today

Public exploit code

CVE Published

Mar 07, 2026 - 05:16 nvd

HIGH 8.8

DescriptionGitHub Advisory

Flowise is a drag & drop user interface to build a customized large language model flow. Prior to version 3.0.13, Flowise 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 privilege. This issue has been patched in version 3.0.13.

Executive ViewAI

Why It Matters

Flowise versions prior to 3.0.13 contain a critical authentication bypass vulnerability that allows attackers with valid tenant credentials to escalate privileges and access unauthorized API functions. Organizations using affected versions face immediate risk of data exfiltration, unauthorized model manipulation, and potential lateral movement within integrated systems.

Business Impact: Severe

Compensating Controls

Deploy Web Application Firewall (WAF) rules to reject or flag HTTP requests containing x-request-from: internal header from non-trusted sources; implement network segmentation to restrict Flowise API access to authorized internal networks only; enforce mutual TLS (mTLS) authentication for all /api/v1/** endpoints; disable the internal request header mechanism if not operationally required; implement continuous API access monitoring and anomaly detection; rotate all service account credentials and tenant tokens immediately.

Threat Intelligence Overview

EPSS Score

0.1%

Top 80% exploitable

Exploit

POC

Public exploit code exists

Data Quality

4 sources

Confidence: Medium

NVD

CVE.org

EPSS

GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC Yes

EPSS 0.1%

Patch available Yes

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.