PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-82640 browser-use CVE debrief

AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-08-30T14:17:03.890Z and has not been modified since then. This vulnerability affects browser-use web-ui versions 2.0.0 through 3.0.0, which store configured LLM API keys in cleartext on disk. The vulnerability allows unauthorized access to sensitive API keys, potentially leading to misuse. Security teams and administrators should verify configurations and take defensive actions to protect API keys. Evidence is limited; verify affected versions and configurations. Check for cleartext API key storage in temporary settings directories.

Vendor
browser-use
Product
web-ui
CVSS
MEDIUM 6.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-30
Original CVE updated
2026-08-30
Advisory published
2026-08-30
Advisory updated
2026-08-30

Who should care

Security teams and administrators responsible for browser-use web-ui installations should verify configurations and take defensive actions to protect API keys. This includes reviewing current configurations, restricting access to temporary settings directories, and monitoring for potential API key misuse.

Technical summary

browser-use web-ui versions 2.0.0 through 3.0.0 store configured LLM API keys in cleartext on disk without encryption or access restrictions. Attackers with read access to temporary settings directories can recover API keys from predictably-named JSON files. This vulnerability allows unauthorized access to sensitive API keys, potentially leading to misuse. The vulnerability has a CVSS score of 6.8 and a severity of MEDIUM. Limited source detail; verify affected scope and configurations.

Defensive priority

Medium-priority defensive tasks are recommended due to the potential for API key exposure.

Recommended defensive actions

  • Inventory and verify configurations of browser-use web-ui versions 2.0.0 through 3.0.0.
  • Check temporary settings directories for cleartext API key storage.
  • Restrict access to temporary settings directories.
  • Monitor for potential API key misuse.
  • Consider upgrading to a version that securely stores API keys.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

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. Evidence is limited; verify affected versions and configurations. Check for cleartext API key storage in temporary settings directories. Limited source detail; verify affected scope and configurations.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-82640 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-82640

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-82640 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-82640

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.