Advisory Database
  • Advisories
  • Dependency Scanning
  1. npm
  2. ›
  3. flowise-components
  4. ›
  5. CVE-2026-43995

CVE-2026-43995: Flowise: SSRF Protection Bypass via Direct node-fetch / axios Usage (Patch Enforcement Failure)

April 16, 2026 (updated May 8, 2026)

Flowise introduced SSRF protections through a centralized HTTP security wrapper (httpSecurity.ts) that implements deny-list validation and IP pinning logic.

However, multiple tool implementations directly import and invoke raw HTTP clients (node-fetch, axiosInstead of using the secured wrapper.

Because enforcement is neither mandatory nor centralized, these tools bypass SSRF mitigation entirely, restoring full SSRF capability even after the patch.

This issue is distinct from specification trust issues and represents incomplete mitigation of previously addressed SSRF vulnerabilities.

References

  • github.com/FlowiseAI/Flowise
  • github.com/FlowiseAI/Flowise/security/advisories/GHSA-qqvm-66q4-vf5c
  • github.com/advisories/GHSA-qqvm-66q4-vf5c
  • nvd.nist.gov/vuln/detail/CVE-2026-43995

Code Behaviors & Features

Detect and mitigate CVE-2026-43995 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions before 3.1.0

Fixed versions

  • 3.1.0

Solution

Upgrade to version 3.1.0 or above.

Impact 6.4 MEDIUM

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Learn more about CVSS

Weakness

  • CWE-918: Server-Side Request Forgery (SSRF)

Source file

npm/flowise-components/CVE-2026-43995.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Sat, 09 May 2026 12:18:24 +0000.