CVE-2026-56275
Flowiseai Flowise server-side request forgery (SSRF)
- Published23 Jun 2026
Description
Flowise before 3.1.0 contains a server-side request forgery vulnerability in the Execute Flow node that allows attackers to bypass security validation by providing intranet addresses through the base URL field. Attackers can initiate HTTP requests to internal network addresses, access cloud metadata, and enumerate internal services by exploiting the missing secureFetch verification in httpSecurity.ts.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:NAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-56275 being actively exploited?
CVE-2026-56275 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.32%.
How severe is CVE-2026-56275?
CVE-2026-56275 has a CVSS 3.1 base score of 7.1, rated high. EPSS estimates a 0.32% probability of exploitation.
Which products are affected by CVE-2026-56275?
Affected products include Flowiseai Flowise.
How do I fix CVE-2026-56275?
Upgrade affected software to a fixed version, for example Flowiseai Flowise 3.1.0 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-56275 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.