# CVE-2026-8026: FlowiseAI Flowise API Response account.service.ts login information disclosure

> Remote attackers can exploit a flaw in the login API to disclose sensitive account information, requiring high complexity to execute.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 May 2026
- **Updated:** 6 May 2026
- **Also known as:** GHSA-8f47-4rh3-x44m

## What is CVE-2026-8026?

CVE-2026-8026 is a medium-severity vulnerability in Flowiseai Flowise, published on 6 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information), CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-8026?

2 open source packages ship an affected version, including flowise. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `flowise` | npm | All versions to 3.0.12 | None |
| `flowise` | npm | All versions to 3.0.12 | None |

Products: Flowiseai Flowise.

## How do I fix CVE-2026-8026?

No fix has been published for CVE-2026-8026 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-8026 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8026 exists.

## Other vulnerabilities in Flowiseai Flowise

- [CVE-2025-71338](https://insights.sbomify.com/CVE-2025-71338/): Flowise through 2.2.7 - Arbitrary File Write to Remote Code Execution via document-store API (critical 10.0)
- [CVE-2026-40933](https://insights.sbomify.com/CVE-2026-40933/): Flowise: Authenticated RCE Via MCP Adapters (critical 10.0)
- [CVE-2025-61913](https://insights.sbomify.com/CVE-2025-61913/): Flowise is vulnerable to arbitrary file read, arbitrary file write (critical 10.0)
- [CVE-2025-59528](https://insights.sbomify.com/CVE-2025-59528/): Flowise has Remote Code Execution vulnerability (critical 10.0)
- [CVE-2026-52098](https://insights.sbomify.com/CVE-2026-52098/): Code injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8026 and fix it if it is affected.

What it is: CVE-2026-8026 is a medium-severity vulnerability in Flowiseai Flowise, published on 6 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8026 exists.

Affected packages and fixed versions:
- flowise (npm): affected all versions up to 3.0.12; no fix listed
- flowise (npm): affected all versions up to 3.0.12; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-8026/ (Markdown: https://insights.sbomify.com/CVE-2026-8026/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-8026
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-8026
- OSV: https://osv.dev/vulnerability/CVE-2026-8026

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-8026/
Summaries are generated and may contain mistakes; the official description above is the record.