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

GHSA-8f47-4rh3-x44m

LOW

GHSA-8f47-4rh3-x44m is a low-severity (CVSS 3.7) Information Exposure vulnerability in flowise. O3 Security confirms whether GHSA-8f47-4rh3-x44m is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Flowise: Bcrypt Password Hash Exposure

Also known asCVE-2026-8026
Published
May 6, 2026
Updated
May 12, 2026
Affected
1 pkg
Patched
None yet
Exploits
None indexed

Real-World Exposure

1 pkg 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

Description

A security flaw has been discovered in FlowiseAI Flowise up to 3.0.12. Affected is the function Login of the file packages/server/src/enterprise/services/account.service.ts of the component API Response Handler. The manipulation results in information disclosure. The attack can be launched remotely. A high complexity level is associated with this attack. The exploitability is told to be difficult. You should upgrade the affected component.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmflowiseall versionsNo fix

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. Remediation status

    No patched version of flowise has shipped for GHSA-8f47-4rh3-x44m yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    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-8f47-4rh3-x44m 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-8f47-4rh3-x44m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A security flaw has been discovered in FlowiseAI Flowise up to 3.0.12. Affected is the function Login of the file packages/server/src/enterprise/services/account.service.ts of the component API Response Handler. The manipulation results in information disclosure. The attack can be launched remotely. A high complexity level is associated with this attack. The exploitability is told to be difficult. You should upgrade the affected component.
O3 Security · Impact-Aware SCA

Is GHSA-8f47-4rh3-x44m in your dependencies?

O3 detects GHSA-8f47-4rh3-x44m across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.