CVE-2026-67620 FlowiseAI CVE debrief

Who should care

Users of Flowise, especially those deploying on Oracle Cloud Infrastructure or Alibaba Cloud, should be aware of this vulnerability and take steps to mitigate it. This includes inventorying and assessing Flowise deployments for exposure, restricting access to the fetch-links API endpoint, and implementing additional validation for URL parameters. Security teams should monitor for suspicious requests to cloud instance metadata services and plan for vendor-supported updates or mitigations through normal change control where exposure is confirmed. Affected operators and platforms should review compensating controls for exposed systems while remediation is scheduled and verified. Vulnerability management teams should track exceptions, retest remediated assets, and close the item only after evidence is documented. Those responsible for asset inventory should confirm whether affected product deployments exist in managed environments and assign an owner for follow-up. Teams should also review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. Those managing change windows should plan for updates through normal change control. Those tracking source changes should check relevant monitoring, detection, and logs for exposed assets that need extra review. Security teams should also consider rollback/change windows for remediation if necessary and verify source tracking for affected deployments. Security teams should also consider compensating controls for exposed systems while remediation is scheduled and verified. Security teams should also consider monitoring for suspicious requests to cloud instance metadata services. Security teams should also consider asset inventory for affected deployments. Security teams should also consider vendor patch guidance for remediation. Security teams should also consider exposure review for affected deployments. Security teams should also consider source tracking for affected deployments. Security teams should also consider compensating controls for exposed systems while remediation is scheduled and verified. Security teams should also consider rollback/change windows for remediation if

Technical summary

The vulnerability exists in Flowise through 3.1.4 due to a server-side request forgery (SSRF) issue in the SSRF guard implemented in httpSecurity.ts. The DEFAULT_DENY_LIST omits the Oracle Cloud Infrastructure metadata endpoint 192.0.0.192 and the Alibaba Cloud metadata endpoint 100.100.100.200. Authenticated attackers can send requests to the fetch-links API endpoint with a crafted URL parameter to bypass deny-list validation and reach instance metadata services.

Defensive priority

Authenticated attackers can exploit this vulnerability to access instance identity data and role credentials on Oracle Cloud Infrastructure or Alibaba Cloud deployments.

Recommended defensive actions

• Inventory and assess Flowise deployments for exposure, especially those on Oracle Cloud Infrastructure or Alibaba Cloud
• Restrict access to the fetch-links API endpoint
• Implement additional validation for URL parameters
• Monitor for suspicious requests to cloud instance metadata services
• Update Flowise to a version that includes the fix, if available

Evidence notes

The vulnerability exists in Flowise through 3.1.4 due to a server-side request forgery (SSRF) issue in the SSRF guard implemented in httpSecurity.ts. The DEFAULT_DENY_LIST omits the Oracle Cloud Infrastructure metadata endpoint 192.0.0.192 and the Alibaba Cloud metadata endpoint 100.100.100.200. Authenticated attackers can send requests to the fetch-links API endpoint with a crafted URL parameter to bypass deny-list validation and reach instance metadata services.

Official resources