VulnerabilityAnalyzed

CVE-2026-70478

An attacker with a credential ID can use the token to access the victim's connected service and can also exhaust refresh-token quota.

CRITICAL 9.2EPSS 0.53%

Does this matter?

High impact if exploited, but EPSS currently rates exploitation as unlikely (0.53%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.

Description

Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, the POST /api/v1/oauth2-credential/refresh/:credentialId endpoint is included in WHITELIST_URLS and requires no authentication. The endpoint decrypts the stored credential, sends a refresh request to the configured OAuth provider with the client secret and refresh token, and returns the refreshed access_token in the response body. An attacker with a credential ID can use the token to access the victim's connected service and can also exhaust refresh-token quota. This issue is fixed in 3.1.3.

CVSS 4.0: 9.2 CRITICALCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/M
EPSS: 0.53% probability · 44th percentile
CISA KEV: Not listed
Weakness: CWE-200
Affected: flowiseai/flowise
Source: security-advisories@github.com

References

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-qgvm-j2hm-6m38Vendor Advisory
https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-qgvm-j2hm-6m38Vendor Advisory

Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.