Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-6wp6-22x5-rr3w

HIGHFix: FlowiseAI/Flowise@e32b643

GHSA-6wp6-22x5-rr3w is a high-severity (CVSS 7.6) Code Injection vulnerability in flowise. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-6wp6-22x5-rr3w is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Flowise vulnerable to code injection via api/v1

Also known asCVE-2024-31621
Published
Apr 29, 2024
Updated
Aug 2, 2024
Affected
1 pkg
Patched
1 / 1
Exploits
1 known

Real-World Exposure

1 pkg affected
📦flowise

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

An issue in FlowiseAI Inc Flowise prior to v1.8.1 allows a remote attacker to execute arbitrary code via a crafted script to the api/v1 component.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmflowiseall versions1.8.1
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-52001webappstypescript

Flowise 1.6.5 - Authentication Bypass

by Maerifat Majeed · Apr 21, 2024

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. Fix

    Update flowise to 1.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6wp6-22x5-rr3w is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-6wp6-22x5-rr3w 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-6wp6-22x5-rr3w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

An issue in FlowiseAI Inc Flowise prior to v1.8.1 allows a remote attacker to execute arbitrary code via a crafted script to the api/v1 component.
O3 Security · Impact-Aware SCA

Is GHSA-6wp6-22x5-rr3w in your dependencies?

O3 detects GHSA-6wp6-22x5-rr3w across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.