{"answers":{"affected":"3 open source packages ship an affected version, including browser-use.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-47241 exists.","fix":"Upgrade browser-use to 0.1.45 or later.","what":"CVE-2025-47241 is a medium-severity vulnerability in browser-use, published on 3 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-47241 and fix it if it is affected.\n\nWhat it is: CVE-2025-47241 is a medium-severity vulnerability in browser-use, published on 3 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-47241 exists.\n\nAffected packages and fixed versions:\n- browser-use (PyPI): affected all versions; fixed in 0.1.45\n- browser-use (PyPI): affected all versions; fixed in 0.1.45\n- browser-use (PyPI): affected all versions; fixed in 0.1.45\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-2025-47241/ (Markdown: https://insights.sbomify.com/CVE-2025-47241/index.md)","id":"CVE-2025-47241","markdown":"https://insights.sbomify.com/CVE-2025-47241/index.md","name":"CVE-2025-47241","record":{"aliases":["GHSA-x39x-9qw5-ghrf","PYSEC-2026-300"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Python browser automation library","requires_auth":"none","summary":"Attackers can bypass allowed_domains restrictions in browser-use by exploiting URL parsing flaws involving userinfo in the authority component.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-647","name":"Use of Non-Canonical URL Paths for Authorization Decisions"}],"description":"In browser-use (aka Browser Use) before 0.1.45, URL parsing of allowed_domains is mishandled because userinfo can be placed in the authority component.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Browser Use allows bypassing `allowed_domains` by putting a decoy domain in http auth username portion of a URL","id":"CVE-2025-47241","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":3,"n_references":3,"next":{"headline":"Auth bypass in ProGet","id":"CVE-2025-47244"},"packages":[{"ecosystem":"PyPI","fixed":["0.1.45"],"introduced":["0"],"last_affected":[],"package":"browser-use","purl":null,"source":"GHSA-x39x-9qw5-ghrf"},{"ecosystem":"PyPI","fixed":["0.1.45"],"introduced":["0"],"last_affected":[],"package":"browser-use","purl":"pkg:pypi/browser-use","source":"GHSA-x39x-9qw5-ghrf"},{"ecosystem":"PyPI","fixed":["0.1.45"],"introduced":["0"],"last_affected":[],"package":"browser-use","purl":"pkg:pypi/browser-use","source":"PYSEC-2026-300"}],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2025-47240"},"products":["browser-use"],"published":"2025-05-03","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-05","vendors":["browser-use"]},"summary":"Attackers can bypass allowed_domains restrictions in browser-use by exploiting URL parsing flaws involving userinfo in the authority component.","url":"https://insights.sbomify.com/CVE-2025-47241/"}