CVE-2026-67620: Flowise SSRF Vulnerability in Metadata Guard
Flowise
Flowise versions up to 3.1.4 contain an SSRF vulnerability where metadata endpoints are omitted from the default deny list. Authenticated attackers can force the server to issue arbitrary GET requests to cloud instance metadata services.
disclosed CVENo confirmed exploitation, so this record is tracked as a disclosed vulnerability and not counted as an incident. It moves into the counts if CISA or the vendor confirms exploitation. Why
- CVSS
- 7.7
- EPSS
- <0.01 · top 60% · 2026-11-13
- fix status
- Fix status unknown
- first report
- 8 Aug 2026
- last update
- 8 Aug 2026
- CVE ids
Timeline · 1
Sources · 1
Advisories and databases
- 2026-08-08CVE-2026-67620: Flowise through 3.1.4 contains a server-side request forgery vulnerability in the SSRF guard implemented in httpSecurity.ts,…NVD · nvd.nist.gov/vuln/detail/CVE-2026-67620
Titles and links belong to their publishers. The summary above is written by gcdRadar in its own words; data is CC BY-SA 4.0.
Classification
- lane
- Patch now
- AI role
- Attack on AI
- categories
- Infrastructure vulnerability
- severity
- 2 · Disclosed vulnerability
- fix status
- Fix status unknown
- targets
- Framework / tooling
- owasp llm top 10
- LLM03:2025 Supply Chain
- mitre atlas
- no technique for these categories
- dates
- happened 8 Aug 2026 · first reported 8 Aug 2026
- origin
- NVDVulnerability record from NVD / the GitHub Advisory Database. This product uses the NVD API but is not endorsed or certified by the NVD.
- record
- confidence 0.95 · created 2026-10-18 10:04Z · updated 2026-10-18 10:04Z
Lane, AI role, categories and severity come from the classifier; the OWASP and ATLAS rows are derived from the categories. How these are assigned
Copy a brief
This record as a short Markdown brief, for a ticket, a chat or a coding agent.
the brief as text
# CVE-2026-67620: Flowise SSRF Vulnerability in Metadata Guard https://gcdradar.vercel.app/incidents/cve-2026-67620-flowise-ssrf-vulnerability-in-metadata-guard · AIR-2026-1270 · closed 2026-08-08 - Lane: Patch now - Severity: 2 (Disclosed vulnerability) - Fix status: Fix status unknown - First reported: 2026-08-08 - AI role: Attack on AI - Products: Flowise - CVE ids: CVE-2026-67620 - CVSS: 7.7 ## Summary Flowise versions up to 3.1.4 contain an SSRF vulnerability where metadata endpoints are omitted from the default deny list. Authenticated attackers can force the server to issue arbitrary GET requests to cloud instance metadata services. ## What to do No action recorded; read the sources below and the vendor's advisory. ## Latest updates - 2026-08-08: CVE-2026-67620: Flowise through 3.1.4 contains a server-side request forgery vulnerability in the SSRF guard implemented in httpSecurity.ts,… (https://nvd.nist.gov/vuln/detail/CVE-2026-67620) ## Sources - 2026-08-08 NVD: CVE-2026-67620: Flowise through 3.1.4 contains a server-side request forgery vulnerability in the SSRF guard implemented in httpSecurity.ts,… https://nvd.nist.gov/vuln/detail/CVE-2026-67620 Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.
Related
- closed8.6Flowise CVE-2026-73484: Flowise pythonCodeValidator sandbox escape vulnerability
Patch now · Disclosed · since 13 Aug 2026 · CVE-2026-73484
AI - closed6.3Flowise CVE-2026-73603: Chatflow visibility bypass in Flowise TTS endpoint
Patch now · Disclosed · since 13 Aug 2026 · CVE-2026-73603
AI - closed9.0Flowise CVE-2026-73486: Code injection in Flowise CSV Agent node
Patch now · Disclosed · since 13 Aug 2026 · CVE-2026-73486
AI - closed7.1Flowise CVE-2026-73604: Incomplete credential redaction in Flowise API
Patch now · Disclosed · since 13 Aug 2026 · CVE-2026-73604
AI - closed9.9Flowise CVE-2026-73602: Sandbox escape and code execution in Flowise
Patch now · Disclosed · since 13 Aug 2026 · CVE-2026-73602
AI - closed9.0Flowise CVE-2026-73601: Remote code execution in Flowise Custom MCP node
Patch now · Disclosed · since 13 Aug 2026 · CVE-2026-73601
AI