Servers and applications
CVE-2026-69250
Unauthenticated OAuth2 Refresh Enables Non-Blind SSRF and Secret Exfiltration
- Severity
- High 8.5
- Published
- 29 Jul 2026
- Last changed
- 23 Oct 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 3.1.3
- Exploit chance
- 0.6% in the next 30 daysHigher than 48% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · Needs an administrator account · No user action needed
- Attacker can
- Read data · Change data
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X- Also known as
- GHSA-r745-8hwv-h473
- Sources
- NVD, Project advisories (GitHub)
Description
The OAuth2 token refresh endpoint (POST /api/v1/oauth2-credential/refresh/:credentialId) is unauthenticated by design (it is in the public whitelist) and performs a server-side HTTP request to a credential-controlled URL (accessTokenUrl) without SSRF protections. In runtime validation, this endpoint was reachable without auth, triggered outbound POST requests to an attacker-controlled server, and reflected the full remote response body to the caller (tokenInfo), confirming non-blind SSRF and credential secret exfiltration.
The vulnerability is in dist/routes/oauth2/index.js (container runtime build), under path prefix /api/v1/oauth2-credential.
Confirmed in runtime code:
- Unauthenticated route via whitelist
- dist/utils/constants.js includes:
- /api/v1/oauth2-credential/callback
- /api/v1/oauth2-credential/refresh
- dist/index.js auth middleware uses:
- const isWhitelisted = whitelistURLs.some((url) => req.path.startsWith(url))
- Therefore…
Affected software
| Software | Affected versions |
|---|---|
FlowiseServers and applications · cpe:a:flowiseai:flowise |
|
FlowiseServers and applications · github:flowiseai/flowise |
|
About Flowise
Build AI Agents, Visually
- Archived
- Yes, no longer maintainedGitHub
- Weekly downloads (npm)
- 6,604npm, 15 Nov 2026
- Docker Hub pulls
- 7,390,661Docker Hub, 15 Nov 2026
- GitHub stars
- 55,573GitHub, 15 Nov 2026
- Forks
- 25,094GitHub, 15 Nov 2026
- Latest release
- [email protected]GitHub, 15 Nov 2026
- Released
- 29 Jul 2026GitHub
- First published on GitHub
- 31 Mar 2023GitHub
Source code Website Docker image Package
Vulnerabilities in Flowise
- In our list
- 171
- Published in the last 12 months
- 149
- Critical, last 12 months
- 41
- High, last 12 months
- 70
- Known exploited
- 0
- CVE-2026-130796Flowise 3.1.3 through 3.1.4 MCP Server Token Disclosure via Public Chatflow EndpointHigh 8.8 17 Nov 2026
- CVE-2026-130615Flowise through 3.1.4 SSRF via DNS Rebinding in Playwright and Puppeteer LoadersHigh 7.6 17 Nov 2026
- CVE-2026-127214Flowise 3.1.4 SSRF Bypass via Custom Function SandboxMedium 6.3 13 Nov 2026
- CVE-2026-119978Flowise through 3.1.4 Custom Function Sandbox Escape RCE via LocalFileStoreCritical 9.0 30 Oct 2026
- CVE-2026-90580A vulnerability was found in FlowiseAI Flowise up to 3.0.2. This vulnerability affects the function axios.post of the file packages/server/src/controllers/evaluations/index.ts of the component Evaluations Endpoint. The manipulation of the argument Host/X-Forwarded-Proto results in server-side request forgery. The attack may be launched remotely. The exploit has been made public and could be…Low 2.1 13 Sept 2026
- CVE-2026-90535Flowise versions before 3.1.4 contain an unauthenticated denial of service vulnerability in the /api/v1/text-to-speech/abort endpoint that accepts user-supplied chatflowId and chatId without ownership verification. Attackers can terminate active chatflow predictions for any user by submitting requests with known chatflow and chat identifiers, causing targeted service disruption.Medium 6.3 12 Sept 2026
References
- NVD https://nvd.nist.gov/vuln/detail/CVE-2026-69250
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-69250
- GitHub Advisory Database https://github.com/advisories/GHSA-r745-8hwv-h473
- github.com https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-r745-8hwv-h473