Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-70636 – Authentication Bypass (OAuth2 Credential Refresh) – Flowise 3.1.4 and earlier

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-70636 is an authentication bypass (CWE-862, Missing Authorization) in FlowiseAI Flowise that lets an unauthenticated network attacker reach the OAuth2 credential refresh endpoint and rotate OAuth tokens for any workspace. It affects Flowise versions through 3.1.4 and is rated High severity.

Technical details

  • Root cause: The OAuth2 refresh endpoint remains in the middleware WHITELIST_URLS, and the authorization check uses prefix-based matching (req.path.startsWith(url)). A request to /api/v1/oauth2-credential/refresh/{credentialId} matches the whitelisted /api/v1/oauth2-credential/refresh prefix and skips authentication.
  • Trigger conditions: An attacker sends a POST request to /api/v1/oauth2-credential/refresh/:credentialId with a valid credential identifier. No authentication, workspace membership, or credential ownership is verified.
  • Attack vector: Network, no authentication or user interaction required.
  • Impact: The handler loads the credential record, decrypts stored OAuth secrets, and performs the OAuth refresh request based solely on the ID parameter — enabling unauthorized mutation of credential state across workspace boundaries. This is a bypass of the earlier CVE-2026-41273.

Affected software

  • FlowiseAI Flowise versions 0 through 3.1.4 (3.1.4 and earlier).

Severity

  • CVSS v3.1 base score: 7.5 (High)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Mitigation and recommended actions

  • Immediate: No fixed release was available at the time of advisory publication; the vendor has published a sunset announcement for Flowise. Monitor vendor channels for an updated release and migration guidance.
  • If no patch: Restrict or block external access to /api/v1/oauth2-credential/refresh/ at a reverse proxy or WAF, place Flowise behind authenticated network controls (VPN/allowlist), and avoid exposing the instance directly to the internet.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: Flowise - Build AI Agents, Visually, Flowise - Low-code LLM apps builder
  • author meta tag content: FlowiseAI
  • description meta tag content: Open source generative AI development platform for building AI agents
  • Raw response body: data-rewardful="9a3a26", og:site_name, flowiseai.com

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge