← Back
CVE-2025-47241
Vulnerability in browser-use (CVE-2025-47241)
Summary
vulnerability in browser-use (CVE-2025-47241). Confidential information can be exposed externally. Exploitable via ``browser_use``. Mitigation: upgrade to `0.1.45` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-47241** has been found in browser-use.
Attackers can target a specific entry point like ``browser_use`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade browser-use to **0.1.45** or later.
If unsure, ask your IT team or search "browser-use CVE-2025-47241" on the vendor's site.
CVE-2025-47241 (browser-use) — CWE-647 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `browser_use` / `BrowserContextConfig` / `allowed_domains`
Patched: `0.1.45` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-647) exists in browser-use. Attackers reach the vulnerable code path via ``browser_use`` without authentication.
📍 Affected scope
browser-use — . Attack surface: `browser_use` / `BrowserContextConfig` / `allowed_domains`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **0.1.45**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'browser-use' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'browser-use' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `browser-use` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade browser-use to 0.1.45ステージング環境で 0.1.45 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
browser-use
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.1.45"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-47241
- package https://github.com/browser-use/browser-use
- web https://github.com/browser-use/browser-use/security/advisories/GHSA-x39x-9qw5-ghrf
- web https://github.com/browser-use/browser-use/pull/1561
- web https://github.com/browser-use/browser-use/releases/tag/0.1.45