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

Back
New CVE Detected

CVE-2026-70478 – Unauthenticated OAuth2 Access Token Exposure – Flowise ≤ 3.1.2

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-70478 is a critical (CVSS 9.2) information-disclosure vulnerability in FlowiseAI’s Flowise, an open-source generative AI development platform. An unauthenticated OAuth2 token refresh endpoint returns freshly issued access tokens to any caller, allowing attackers to steal tokens for connected third-party services. It affects all Flowise versions up to and including 3.1.2.

Technical details

  • Root cause: The endpoint POST /api/v1/oauth2-credential/refresh/:credentialId is included in WHITELIST_URLS, so it requires no authentication. It decrypts stored credentials and returns a newly issued OAuth2 access token directly in the response without verifying the requester’s identity (CWE-200).
  • Trigger conditions: An attacker obtains a credential ID (for example through public chatflow leaks or enumeration) and calls the refresh endpoint.
  • Attack vector: Network — no authentication, privileges, or user interaction required.
  • Impact: Theft of OAuth2 access tokens for connected services, exposure of client secrets during refresh operations, compromise of the victim’s integrated third-party accounts, and potential denial of service through refresh-token quota exhaustion.

Affected software

  • Flowise (npm flowise) versions ≤ 3.1.2.

Severity

  • CVSS 4.0 base score: 9.2 (Critical)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade to Flowise 3.1.3, which fixes the vulnerability.
  • If no patch: Restrict network access to the Flowise instance to authenticated, authorized users only; block or require authentication in front of the /api/v1/oauth2-credential/refresh/ endpoint at a reverse proxy; and rotate any OAuth2 credentials that may have been exposed.

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
  • Meta tag content — author: FlowiseAI; description: 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