Is CVE-2026-8026 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-8026 being exploited in the wild.

How severe is CVE-2026-8026?

Low severity, with a CVSS score of 3.7, published 6 May 2026.

Which products and versions are affected?

flowise (npm) <= 3.0.12, SEMVER:introduced=0,last_affected=3.0.12.

Is there a fix for CVE-2026-8026?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-8026 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-8026?

Check whether you run FlowiseAI Flowise or flowise (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-8026: FlowiseAI Flowise bcrypt password hash exposure in API responses

Q: Which products and versions are affected?

flowise (npm) <= 3.0.12, SEMVER:introduced=0,last_affected=3.0.12.

Q: Is there a fix for CVE-2026-8026?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

Q: How is CVE-2026-8026 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-8026?

Check whether you run FlowiseAI Flowise or flowise (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-8026 · Severity: low · CVSS 3.7 · Published 2026-05-06

Flowise, an open-source tool for building LLM-based applications, contains a security flaw where it inadvertently includes sensitive user data in its API responses. When a user logs in or is invited to the platform, the system returns the encrypted version (hash) of their password to the requester. An attacker could collect these hashes and use specialized hardware to attempt to crack them, potentially gaining full access to user accounts and the sensitive AI workflows they manage.

Technologies: FlowiseAI Flowise, flowise (npm). Vendors: FlowiseAI, npm.

Quick answers

Is CVE-2026-8026 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-8026 being exploited in the wild.
How severe is CVE-2026-8026?: Low severity, with a CVSS score of 3.7, published 6 May 2026.
Which products and versions are affected?: flowise (npm) <= 3.0.12, SEMVER:introduced=0,last_affected=3.0.12.
Is there a fix for CVE-2026-8026?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-8026 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-8026?: Check whether you run FlowiseAI Flowise or flowise (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A sensitive information disclosure vulnerability exists in FlowiseAI Flowise (up to 3.0.12) within the API Response Handler. Specifically, the `login()` and `saveInviteAccount()` functions in `packages/server/src/enterprise/services/account.service.ts` fail to sanitize user objects before returning them to the client. This results in the `credential` field (containing the bcrypt password hash), `tempToken`, and `tokenExpiry` being included in the JSON response body of the `/api/v1/account/login` and `/api/v1/account/invite` endpoints. While the attack complexity is rated as high due to the requirement of specific API interactions, a remote attacker can harvest these hashes for offline brute-force or dictionary attacks. This issue is a regression or incomplete fix of a previous security patch (PR #5167) that introduced a `sanitizeUser()` function but failed to apply it to all relevant authentication pathways. Users are advised to upgrade to a version beyond 3.0.12.

Affected products

FlowiseAI Flowise <= 3.0.12

Identifiers

CVE-2026-8026
GHSA-8f47-4rh3-x44m

Timeline

2026-03-05: other: Vulnerability discovered and PoC created by researcher
2026-05-06: disclosed: NVD and VulDB disclosure
2026-05-06: advisory: GitHub Advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.