How severe is GHSA-qqvm-66q4-vf5c?

No CVSS score has been assigned to GHSA-qqvm-66q4-vf5c yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qqvm-66q4-vf5c?

GHSA-qqvm-66q4-vf5c affects the following packages: flowise (npm), flowise-components (npm). Ecosystems affected: npm.

How do I fix GHSA-qqvm-66q4-vf5c?

Update flowise to 3.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qqvm-66q4-vf5c is resolved across your whole dependency graph.

How do I detect GHSA-qqvm-66q4-vf5c in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for flowise. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-qqvm-66q4-vf5c if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-qqvm-66q4-vf5c?

O3 pinpoints whether GHSA-qqvm-66q4-vf5c is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-qqvm-66q4-vf5c actively exploited in the wild?

No public exploit code has been indexed for GHSA-qqvm-66q4-vf5c yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-qqvm-66q4-vf5c published, and has it been updated?

GHSA-qqvm-66q4-vf5c was published on April 16, 2026 and was last updated on May 13, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-qqvm-66q4-vf5c

GHSA-qqvm-66q4-vf5c is a security vulnerability in flowise. O3 Security confirms whether GHSA-qqvm-66q4-vf5c is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

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

Also known asCVE-2026-43995

Published

Apr 16, 2026

Updated

May 13, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of May 13, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

flowisenpm

4Kdownloads / week

flowise-componentsnpm

4Kdownloads / week

Description

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 requests in these components are executed without SSRF validation.

This renders the mitigation introduced in GHSA-2x8m-83vc-6wv4 incomplete.

Root Cause

Security enforcement is not centralized.

Outbound request validation depends on voluntary usage of a wrapper function rather than being structurally enforced.

Because direct imports of HTTP clients are allowed, the mitigation is easily bypassed.

This is an architectural enforcement failure rather than a single implementation bug.

PoC

Even when an administrator configures:

HTTP_DENY_LIST=169.254.0.0/16,127.0.0.0/8

The following attack succeeds if a vulnerable tool is enabled:

Chat Prompt:

Use the Web Scraper tool to retrieve:
http://169.254.169.254/latest/meta-data/iam/security-credentials/

Execution flow:

The LLM triggers WebScraperTool.
The tool calls raw fetch() directly.
No httpSecurity.ts validation is applied.
The request reaches the metadata endpoint.
The response is returned to the chat context.

This demonstrates that SSRF protection is opt-in rather than enforced.

Impact

Severity: Critical (CVSS v3.1: 9.1 – AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N)

This issue:

Completely bypasses the centralized SSRF mitigation.
Allows access to internal network resources.
Enables the exploitation of cloud metadata and credential theft.
Invalidates the security assumptions of the recent patch.

Any deployment enabling affected tools remains vulnerable.

Recommended Remediation

Refactor all tools to use the centralized secureFetch() wrapper.
Add ESLint no-restricted-imports rules to prohibit the direct usage of node-fetch or axios in tool components.
Consider implementing a single internal HTTP client abstraction layer.
Apply network-level egress filtering as defense-in-depth.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`flowise`	all versions	3.1.0
📦npm	`flowise-components`	all versions	3.1.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for flowise. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update flowise to 3.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qqvm-66q4-vf5c is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-qqvm-66q4-vf5c is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-qqvm-66q4-vf5c. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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`, `axios`Instead 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 vulne

O3 Security · Impact-Aware SCA

Is GHSA-qqvm-66q4-vf5c in your dependencies?

O3 detects GHSA-qqvm-66q4-vf5c across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works