{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-82640 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-82640 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-82640 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-82640 in the wild and no public exploit code.\n\nAffected product: browser-use web-ui. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-82640/ (Markdown: https://insights.sbomify.com/CVE-2026-82640/index.md)","id":"CVE-2026-82640","markdown":"https://insights.sbomify.com/CVE-2026-82640/index.md","name":"CVE-2026-82640","record":{"aliases":["GHSA-jrjf-ww9v-c67g"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"browser-use web-ui","requires_auth":"low_privilege","summary":"Attackers with local read access can recover cleartext LLM API keys from predictable JSON files in the browser-use web-ui settings directory.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":6.8,"severity":"medium","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"browser-use web-ui 2.0.0 through 3.0.0 Cleartext API Key Storage","id":"CVE-2026-82640","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Keploy 3.1.0-3.6.25 Unauthenticated TLS Key Exposure","id":"CVE-2026-82641"},"packages":[],"prev":{"headline":"NextChat 2.15.8 through 2.16.1 OpenAI API Key Disclosure","id":"CVE-2026-82639"},"products":["web-ui"],"published":"2026-08-30","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-24","vendors":["browser-use"]},"summary":"Attackers with local read access can recover cleartext LLM API keys from predictable JSON files in the browser-use web-ui settings directory.","url":"https://insights.sbomify.com/CVE-2026-82640/"}