CVE-2026-41273: Flowise: Unauthenticated OAuth 2.0 Access Token Disclosure via Public Chatflow in Flowise

CVE-2026-41273 · Severity: high · CVSS 8.2 · Published 2026-04-23

Flowise is a platform for building AI-powered conversational workflows that allows organizations to deploy public chatbots. An unauthenticated attacker can exploit two missing authentication checks to obtain OAuth 2.0 access tokens for third-party services (like Gmail) configured within the platform. This could enable unauthorized access to connected accounts, data breaches, or API abuse on behalf of the organization.

Technologies: FlowiseAI Flowise, flowise (npm). Vendors: FlowiseAI, npm.

Quick answers

Is CVE-2026-41273 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-41273 being exploited in the wild.
How severe is CVE-2026-41273?
High severity, with a CVSS score of 8.2, published 23 April 2026.
Which products and versions are affected?
flowise (npm) <= 3.0.13, SEMVER:introduced=0,fixed=3.1.0.
Is there a fix for CVE-2026-41273?
Yes. flowise (npm): upgrade to 3.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-41273 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-41273?
Check whether you run FlowiseAI Flowise or flowise (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • flowise (npm): upgrade to 3.1.0 or later
    npm install flowise@3.1.0

Technical details

Flowise contains an authentication bypass involving two chained API endpoints: GET /api/v1/public-chatbotConfig/<chatflowId> returns internal flowData without authentication, exposing OAuth credential identifiers; POST /api/v1/oauth2-credential/refresh/<credentialId> refreshes OAuth 2.0 tokens without authentication or authorization checks. An attacker can retrieve the credential identifier from the first endpoint and use it with the second endpoint to obtain valid OAuth 2.0 access tokens. This affects self-hosted deployments because public chatflows are intentionally exposed to unauthenticated users via public URLs. The vulnerability is mitigated in version 3.1.0 and later.

Affected products

  • FlowiseAI Flowise <=3.0.13

Identifiers

  • CVE-2026-41273
  • GHSA-6f7g-v4pp-r667

Timeline

  • 2026-04-16: disclosed
  • 2026-04-16: patched: Version 3.1.0 patches the vulnerability

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.