Flowise versions before 3.1.0 contain a server-side request forgery (SSRF) vulnerability in the Execute Flow node. (CVE-2026-56275)
Flowise versions before 3.1.0 contain a server-side request forgery (SSRF) vulnerability in the Execute Flow node. This flaw allows attackers to bypass security validation by submitting intranet addresses via the base URL field, enabling unauthorized HTTP requests to internal network resources. The vulnerability arises from missing secureFetch verification in the httpSecurity.ts component.
AI Analysis
Technical Summary
The vulnerability identified as CVE-2026-56275 affects Flowise prior to version 3.1.0. It is a server-side request forgery (CWE-918) issue in the Execute Flow node, where attackers can bypass security checks by providing intranet addresses in the base URL field. This enables them to initiate HTTP requests to internal network addresses, access cloud metadata services, and enumerate internal services. The root cause is the absence of secureFetch verification in the httpSecurity.ts file, which fails to properly validate or restrict outbound requests initiated by the application.
Potential Impact
Exploitation of this vulnerability could allow an attacker with limited privileges to make unauthorized HTTP requests from the server to internal network addresses. This can lead to information disclosure such as cloud metadata access and internal service enumeration. There is no indication of direct remote code execution or privilege escalation from the provided data. No known exploits are reported in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no patch or official fix information is provided, users should monitor vendor communications for updates. Until a fix is available, restrict access to the affected functionality and consider network-level controls to limit server outbound requests to trusted destinations.
Flowise versions before 3.1.0 contain a server-side request forgery (SSRF) vulnerability in the Execute Flow node. (CVE-2026-56275)
Description
Flowise versions before 3.1.0 contain a server-side request forgery (SSRF) vulnerability in the Execute Flow node. This flaw allows attackers to bypass security validation by submitting intranet addresses via the base URL field, enabling unauthorized HTTP requests to internal network resources. The vulnerability arises from missing secureFetch verification in the httpSecurity.ts component.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability identified as CVE-2026-56275 affects Flowise prior to version 3.1.0. It is a server-side request forgery (CWE-918) issue in the Execute Flow node, where attackers can bypass security checks by providing intranet addresses in the base URL field. This enables them to initiate HTTP requests to internal network addresses, access cloud metadata services, and enumerate internal services. The root cause is the absence of secureFetch verification in the httpSecurity.ts file, which fails to properly validate or restrict outbound requests initiated by the application.
Potential Impact
Exploitation of this vulnerability could allow an attacker with limited privileges to make unauthorized HTTP requests from the server to internal network addresses. This can lead to information disclosure such as cloud metadata access and internal service enumeration. There is no indication of direct remote code execution or privilege escalation from the provided data. No known exploits are reported in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no patch or official fix information is provided, users should monitor vendor communications for updates. Until a fix is available, restrict access to the affected functionality and consider network-level controls to limit server outbound requests to trusted destinations.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-w4hm-rrxg-pxcf
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-56275"]
- Ecosystems
- []
- Database Specific Severity
- MODERATE
- Cvss Version
- 4.0
Threat ID: 6a3ef7ed27e9c79719033aa9
Added to database: 06/26/2026, 22:06:37 UTC
Last enriched: 06/26/2026, 22:48:37 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 22
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.