CVE-2026-82640

browser-use web-ui 2.0.0 through 3.0.0 Cleartext API Key Storage

Published Aug 30, 2026 CVSS 4.0 · 6.8 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The flaw in browser‑use web‑ui causes the system to write configured LLM API keys to disk as plain‑text JSON files without encryption or access restrictions. This permits an attacker who can read the temporary settings directory to recover the keys. The weakness is a clear‑text storage of sensitive information (CWE-312), which could lead to a confidentiality breach of credentials that unlock external LLM services for unauthorized use. The impact is mainly the exposure of those credentials, potentially enabling abuse or cost escalation.

Affected Systems

The vulnerability affects browser‑use web‑ui versions 2.0.0 through 3.0.0. It has been identified in the webui_manager.py component and causes keys to be stored in a predictable temp settings location. No other vendors or product lines are listed as affected.

Risk and Exploitability

The CVSS score of 6.8 indicates a moderate severity. The EPSS score is not available, so the current likelihood of exploitation is unclear. This issue is not listed in the CISA KEV catalog. Attack can occur via a local file‑read vector: an attacker with read access to the temporary settings directory can retrieve the keys. Because the vulnerability does not rely on network exposure, exploitation requires either local or privileged access, making the risk moderate but still significant for hosts with broad temporary directory permissions.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Restrict the permissions of the temporary settings directory so that only the web‑ui process and authorized administrators can read files there.
  • Delete any existing cleartext API key files from that directory or encrypt them with a strong local encryption method.
  • Configure your LLM provider API keys through a secure channel such as environment variables, vault services, or encrypted storage.

Generated by OpenCVE AI on August 30, 2026 at 15:37 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Browser-use web-ui
Vendors & Products Browser-use web-ui
Type Values Removed Values Added
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.
Title browser-use web-ui 2.0.0 through 3.0.0 Cleartext API Key Storage
First Time appeared Browser-use
Browser-use browser Use
Weaknesses CWE-312
CPEs cpe:2.3:a:browser-use:browser_use:*:*:*:*:*:*:*:*
Vendors & Products Browser-use
Browser-use browser Use
References
Metrics cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}

cvssV4_0

{'score': 6.8, 'vector': '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'}

Weaknesses
  • CWE-312

    Cleartext Storage of Sensitive Information

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Sep 24, 2026, 2:20 PM
Reserved
Aug 30, 2026, 1:06 PM
Status
Deferred
Published
Aug 30, 2026, 2:17 PM
Modified
Sep 10, 2026, 3:53 PM