# CVE-2026-82640: browser-use web-ui 2.0.0 through 3.0.0 Cleartext API Key Storage

> Attackers with local read access can recover cleartext LLM API keys from predictable JSON files in the browser-use web-ui settings directory.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Aug 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-jrjf-ww9v-c67g

## What is CVE-2026-82640?

CVE-2026-82640 is a medium-severity vulnerability in browser-use web-ui, published on 30 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

browser-use web-ui versions 2.0.0 through 3.0.0 write configured LLM API keys to disk in cleartext without encryption or access restrictions. Attackers with read access to the temporary settings directory can recover provider API keys from predictably-named JSON files.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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


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

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

## Is CVE-2026-82640 being exploited?

There is no known exploitation of CVE-2026-82640 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82640 is a medium-severity vulnerability in browser-use web-ui, published on 30 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-82640 in the wild and no public exploit code.

Affected product: browser-use web-ui. 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-2026-82640/ (Markdown: https://insights.sbomify.com/CVE-2026-82640/index.md)
```

## Sources

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

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