# CVE-2026-70636: Flowise 3.1.4 Authentication Bypass via OAuth2 Credential Refresh Endpoint

> Unauthenticated attackers can bypass authentication to trigger unauthorized OAuth token rotation, disrupting integrations in Flowise AI.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-rm9r-9424-cccf

## What is CVE-2026-70636?

CVE-2026-70636 is a high-severity authentication bypass vulnerability in Flowiseai Flowise, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Flowise through 3.1.4 contains an authentication bypass vulnerability that allows unauthenticated attackers to access the OAuth2 credential refresh endpoint by exploiting prefix-based whitelist matching in the authentication middleware defined in packages/server/src/utils/constants.ts. Attackers can send a POST request to the oauth2-credential refresh route with a trailing credential identifier to bypass all authentication and authorization checks, triggering unauthorized OAuth token rotation against credentials belonging to any workspace and potentially disrupting dependent OAuth integrations. This is a bypass of CVE-2026-41273.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-70636?

It affects 1 product.


Products: Flowiseai Flowise.

## How do I fix CVE-2026-70636?

No fix has been published for CVE-2026-70636 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-70636 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-70636 exists.

## Other vulnerabilities in Flowiseai Flowise

- [CVE-2025-71338](https://insights.sbomify.com/CVE-2025-71338/): Flowise through 2.2.7 - Arbitrary File Write to Remote Code Execution via document-store API (critical 10.0)
- [CVE-2026-40933](https://insights.sbomify.com/CVE-2026-40933/): Flowise: Authenticated RCE Via MCP Adapters (critical 10.0)
- [CVE-2025-61913](https://insights.sbomify.com/CVE-2025-61913/): Flowise is vulnerable to arbitrary file read, arbitrary file write (critical 10.0)
- [CVE-2025-59528](https://insights.sbomify.com/CVE-2025-59528/): Flowise has Remote Code Execution vulnerability (critical 10.0)
- [CVE-2026-52098](https://insights.sbomify.com/CVE-2026-52098/): Code injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-70636 and fix it if it is affected.

What it is: CVE-2026-70636 is a high-severity authentication bypass vulnerability in Flowiseai Flowise, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-70636 exists.

Affected product: Flowiseai Flowise. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-70636/ (Markdown: https://insights.sbomify.com/CVE-2026-70636/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-70636
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-70636
- OSV: https://osv.dev/vulnerability/CVE-2026-70636

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-70636/
Summaries are generated and may contain mistakes; the official description above is the record.