Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-43995 critical CVSS 9.8

SSRF (Server-Side Request Forgery) in flowise (CVE-2026-43995)

Summary

SSRF in flowise (CVE-2026-43995). Successful exploitation can lead to full system takeover. Exploitable via httpSecurity.ts. Mitigation: upgrade to 3.1.0 or later.

Original description

The description as published by the source.

Summary

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.

Details

Intended Security Model:

All outbound HTTP requests should pass through the centralized validation layer implemented in:

packages/components/src/httpSecurity.ts

This layer performs:

  • HTTP_DENY_LIST enforcement
  • IP resolution validation
  • IP pinning
  • Loopback blocking

Observed Implementation Gap:

Multiple tools bypass this layer and import HTTP libraries directly.

Examples include:

  • packages/components/nodes/tools/OpenAPIToolkit/OpenAPIToolkit.ts
  • packages/components/nodes/tools/WebScraperTool/WebScraperTool.ts
  • packages/components/nodes/tools/MCP/core.ts
  • packages/components/nodes/tools/Arxiv/core.ts

These files directly execute:

importfetchfrom'node-fetch'

or invoke axios without passing through the centralized validation wrapper.

Because there is no global interceptor or enforcement mechanism, outbound requ…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-43995 has been found in flowise.
Attackers can target a specific entry point like httpSecurity.ts over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade flowise to 3.1.0 or later.
If unsure, ask your IT team or search "flowise CVE-2026-43995" on the vendor's site.

CVE-2026-43995 (flowise) — CWE-918 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: httpSecurity.ts / axios / HTTP_DENY_LIST / WebScraperTool
Patched: 3.1.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

SSRF (CWE-918) exists in flowise. Attackers reach the vulnerable code path via httpSecurity.ts without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of flowise. Attack surface: httpSecurity.ts / axios / HTTP_DENY_LIST / WebScraperTool.

🔥 Severity

Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 3.1.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'flowise' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'flowise' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で flowise を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade flowise to 3.1.0

    ステージング環境で 3.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm flowise
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.1.0"}]}]
npm flowise-components
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.1.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details