CVE-2026-69250 is a high severity (CVSS 7.5) server side request flaw in Flowise, the drag and drop LLM flow builder. Before 3.1.3, an unauthenticated OAuth2 token refresh endpoint makes outbound requests to a credential defined URL and returns the response body. Upgrade to Flowise 3.1.3.
What's affected
The record says Flowise before 3.1.3 is affected, and that the issue is fixed in 3.1.3. Fixed in Flowise 3.1.3, which the project published as a GitHub release. The release page I retrieved shows the repository as archived and read only by its owner since 13 August 2026. That does not change the advice to run 3.1.3 or later, but it does mean you should check where future security fixes will come from before you rely on this project long term.
The affected route is the OAuth2 credential refresh endpoint. The record says it is unauthenticated by design and sends a server side HTTP request to the token URL stored in the credential, without SSRF protections. In the record's words, runtime validation confirmed the response body is reflected to the caller, and that the outbound request body carries client identifier, client secret, grant type and refresh token values.
I relied on the record for the technical description of this CVE. The 3.1.3 release page was the only vendor page I retrieved, and it does not give a per-CVE explanation.
How to check if you're exposed
npm ls -g flowise
docker image ls | grep -i flowise
The first command shows a global npm install, the second any Flowise container image and its tag. If you run it from a compose file or a Kubernetes manifest, read the image tag there. Anything below 3.1.3 is in scope.
Then find who can reach the affected feature. In most deployments the first control is who holds a login or an API key, so list those too. Every path described in the record needs some level of access, or in the unauthenticated case, only network reach to the service.
A quicker route for a whole project is the free in-browser dependency scan at Gold. Paste a manifest or lockfile and it matches each dependency against known CVEs, including ones pulled in indirectly.
What to do now
- Upgrade Flowise to 3.1.3 or later and redeploy all instances, including containers built from older images.
- Rotate OAuth client secrets and refresh tokens stored in Flowise credentials, starting with any on instances reachable from outside your network.
- Block access to the refresh route at your reverse proxy until you have upgraded.
- Restrict outbound traffic from the Flowise host to the addresses it needs, to limit server side request abuse.
- Check outbound request logs for unexpected destinations.
- Check whether the project's archived status affects your support plan, and decide on an owner for security updates.
- Run Flowise behind authentication and a network boundary, and do not expose its admin or API ports directly to the internet.
Reachability analysis helps with ordering the work. Knowing whether your code actually calls the affected path tells you which services to patch first.
Why it matters
The record tags this as CWE-639, authorization bypass through a user controlled key, though its text describes a server side request forgery. Both point at the same design gap: an endpoint that needs no login, takes an identifier that selects stored data, and makes a network call on the server's behalf.
Two harms follow from what the record describes. The server can be used to reach internal addresses, and the OAuth credentials stored in Flowise can be sent to a destination of the caller's choosing. Treat stored OAuth secrets and refresh tokens as exposed if you ran an affected instance on a reachable network. The record does not mark this CVE as known exploited.
Quick check
Does an attacker need to log in?
The record says the endpoint is reachable without authentication.
What should I rotate?
OAuth client secrets and refresh tokens stored as Flowise credentials, if the instance was reachable by untrusted clients.
Sources
- https://github.com/FlowiseAI/Flowise/releases/tag/flowise@3.1.3
- Record: NVD entry for CVE-2026-69250 (score 7.5, HIGH)
Last reviewed: 18 October 2026.
