CVE-2026-43995 is a critical server side request forgery flaw (CVSS 9.8) in Flowise. Several built in tools call raw HTTP clients instead of the secured wrapper, so SSRF protections do not apply to them. The advisory lists flowise-components up to 3.0.13 as affected and 3.1.0 as the fix.
What's affected
The advisory lists flowise-components on npm at 3.0.13 and earlier, patched in 3.1.0. The NVD record words it as before 3.1.0.
The tools named are the OpenAPI toolkit, the web scraper tool, the MCP core and the Arxiv tool.
How to check if you're exposed
npm ls flowise flowise-components
For Docker, read the image tag. Then review your flows for use of the four tools named above, and check where the server runs and what it can reach, since SSRF is about reaching internal addresses.
What to do now
- Upgrade Flowise and flowise-components to 3.1.0 or later.
- Keep the Flowise server off the public internet, or require authentication in front of it.
- Block outbound requests from the host to internal ranges and cloud metadata addresses.
- Review flows that use the OpenAPI, scraper, MCP and Arxiv tools.
- Rotate any credentials the server could reach if you suspect misuse.
Why it matters
The weakness is CWE-918, server side request forgery. Flowise built a central module with deny lists, IP validation and pinning, but its use was optional. Four tools bypassed it and called node-fetch or axios directly.
The advisory calls this an incomplete fix for earlier SSRF issues. A safety control that is not mandatory in the code path is easy to bypass by accident. The KEV flag is false.
Quick check
Why did the earlier protection not help?
Per the advisory, those tools never called the secured wrapper, so its checks never ran.
Sources
Last reviewed: 19 October 2026.
