CVE-2026-30820
Privilege escalation via trusted header bypass in Flowise API (pre-3.0.13).
Is CVE-2026-30820 being exploited?
Not confirmed. CVE-2026-30820 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.48% probability of exploitation in the next 30 days.
How severe is CVE-2026-30820?
CVE-2026-30820 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-30820?
Yes. A fix has been recorded for CVE-2026-30820. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-30820 affect?
CVE-2026-30820 affects Flowise. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-30820?
Upgrade to 3.0.13+; verify admin endpoints; rotate credentials if exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Low-priv tenant can bypass API auth with x-request-from: internal and reach internal admin endpoints (API keys, credentials, custom function execution) via cookie.
Patch when possible
- affected< 3.0.13
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.