On this page

Atomicorp WAF Research Note: CVE-2026-67620

CVE Details

Status: Attack Blocked by Atomicorp
  • Already protected by existing Atomicorp WAF rules
  • Protection status: Understanding Atomicorp WAF Protection Status
  • CVE: CVE-2026-67620
  • Name: Flowise 3.1.4 SSRF via fetch-links Endpoint Incomplete Deny-List
  • Severity: Medium
  • CVSS: 6.3 (v4.0) (Medium)
  • CVSS version: 4.0
  • CVSS source: VulnCheck CNA
  • CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/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
    • Attack vector: Network
    • Attack complexity: Low
    • Attack requirements: None
    • Privileges required: Low
    • User interaction: None
    • Vulnerable-system confidentiality: None
    • Vulnerable-system integrity: None
    • Vulnerable-system availability: None
    • Subsequent-system confidentiality: High
    • Subsequent-system integrity: None
    • Subsequent-system availability: None
    • Scope: X
  • CWE: CWE-918 — Server-Side Request Forgery (SSRF)
  • Related CAPEC attack patterns (via MITRE CWE relationships): CAPEC-664
  • Vendor: flowiseai
  • Vulnerable product: flowise
  • CVE published: 2026-08-08
  • CVE last modified: 2026-09-04
  • Affected versions (NVD configurations):
    • flowise: <= 3.1.4
  • EPSS: 0.0032; 24.7th percentile (FIRST )
  • Latest Update: 2026-09-06
  • Selected Rule IDs observed: 337109 , 337110 , 340165 , 344360 , 347009 , 390722 , 398001 , 398021 , 398022
  • Matching rules: 9; rules with blocking actions: 8
  • Would-block Rule IDs: 337109 , 337110 , 340165 , 344360 , 347009 , 390722 , 398021 , 398022
  • Request surfaces inspected: JSON request data, Request URI, Request argument names, Request arguments, Request cookies, SOAP request data, XML request data
Technical CPE data

This section lists vulnerable CPE matches retained from the NVD configurations. It supplements the readable affected-product information above.

  • cpe:2.3:a:flowiseai:flowise:*:*:*:*:*:*:*:*
    • Version end (inclusive): 3.1.4
    • NVD match criteria ID: 9B13DD07-EC62-44CC-8602-EEAE7960C9B3

Vulnerability Description

Flowise through 3.1.4 contains a server-side request forgery vulnerability in the SSRF guard implemented in httpSecurity.ts, where 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, 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.

  1. Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (337109 , 337110 , 340165 , 344360 , 347009 , 390722 , 398021 , 398022 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.

  2. Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.

  3. Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.

Research Notes

Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.

Public Vulnerability References

Test or Research Source

  • Source: Atomicorp AI Research Framework
  • Tags: cve, derived, ssrf, waf-probe

Research Note Context

This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.

Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.

Learn More

Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.

Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:

  • Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
  • Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
  • Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
  • Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
  • Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.

For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ .