# CVE-2025-59434: Critical Multi-Tenant Variable Disclosure in Flowise Cloud via Custom JavaScript Function

> Authenticated users on the free tier can access sensitive environment variables and secrets from other tenants via a custom JavaScript function.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2025
- **Updated:** 22 Sep 2025

## What is CVE-2025-59434?

CVE-2025-59434 is a critical vulnerability in FlowiseAI Flowise, published on 22 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Flowise is a drag & drop user interface to build a customized large language model flow. Prior to August 2025 Cloud-Hosted Flowise, an authenticated vulnerability in Flowise Cloud allows any user on the free tier to access sensitive environment variables from other tenants via the Custom JavaScript Function node. This includes secrets such as OpenAI API keys, AWS credentials, Supabase tokens, and Google Cloud secrets — resulting in a full cross-tenant data exposure. This issue has been patched in the August 2025 Cloud-Hosted Flowise.

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

## Which versions are affected by CVE-2025-59434?


## How do I fix CVE-2025-59434?

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

## Is CVE-2025-59434 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59434 and fix it if it is affected.

What it is: CVE-2025-59434 is a critical vulnerability in FlowiseAI Flowise, published on 22 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59434 exists.

Affected product: FlowiseAI Flowise. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2025-59434/ (Markdown: https://insights.sbomify.com/CVE-2025-59434/index.md)
```

## Sources

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

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