CVE-2026-67620: Flowise 3.1.4 SSRF via fetch-links Endpoint Incomplete Deny-List
Flowise through 3.1.4 contains a server-side request forgery vulnerability in the SSRF guard implemented in httpSecurity.ts, where the DEFAULTDENYLIST omits the Oracle Cloud Infrastructure metadata endpoint 192.0.0.192 and the Alibaba Cloud metadata endpoint 100.100.100.200, allowing authenticated attackers to force the server to issue arbitrary GET requests to cloud instance metadata services. Attackers can send requests to the fetch-links API endpoint with a crafted URL parameter, bypassing deny-list validation including redirect-based bypasses, to reach instance metadata services and expose instance identity data and role credentials on Oracle Cloud Infrastructure or Alibaba Cloud deployments, with unauthenticated access possible when URL-fetching nodes exist in public chatflows.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-67620?
The severity of CVE-2026-67620 is high with a score of 7.7.
What type of vulnerability is CVE-2026-67620?
CVE-2026-67620 is a server-side request forgery (SSRF) vulnerability.
How do I fix CVE-2026-67620?
To fix CVE-2026-67620, update Flowise to version 3.1.5 or later, which includes a complete deny-list.
What impact does CVE-2026-67620 have?
CVE-2026-67620 can allow authenticated users to access unauthorized internal services and metadata endpoints.
Which versions of Flowise are affected by CVE-2026-67620?
CVE-2026-67620 affects all versions of Flowise up to and including 3.1.4.