KEVWire

Security intelligence, with context.

Response snapshot Oct 27, 2026, 16:31 UTC

Back to the wire
Permalink
VulnerabilityCVE-2025-47241

Browser Use allows bypassing `allowed_domains` by putting a decoy domain in http auth username portion of a URL

The `BrowserContextConfig` class defines an `allowed_domains` list, which is intended to limit accessible domains.

Published Updated

At a glance

Exploited
Not known
Severity
9.3 Critical (CVSS 3.1)
Chance of exploitation
Not estimated
Sources
1 source

What to do

GitHub lists first patched versions: browser-use: 0.1.45. Confirm the affected range and upgrade guidance in the exact advisory.

Read GitHub-reviewed advisory GHSA-x39x-9qw5-ghrf (opens a new tab)

What happened

### Summary During a manual source code review, [**ARIMLABS.AI**](https://arimlabs.ai) researchers identified that the `browser_use` module includes an embedded whitelist functionality to restrict URLs that can be visited. This restriction is enforced during agent initialization. However, it was discovered that these measures can be bypassed, leading to severe security implications.

### Details **File:** `browser_use/browser/context.py`

The `BrowserContextConfig` class defines an `allowed_domains` list, which is intended to limit accessible domains. This list is checked in the `_is_url_allowed()` method before navigation:

```python @dataclass class BrowserContextConfig: """ [STRIPPED] """ cookies_file: str | None = None minimum_wait_page_load_time: float = 0.5 wait_for_network_idle_page_load_time: float = 1 maximum_wait_page_load_time: float = 5 wait_between_actions: float = 1

Continue reading

disable_security: bool = True

browser_window_size: BrowserContextWindowSize = field(default_factory=lambda: {'width': 1280, 'height': 1100}) no_viewport: Optional[bool] = None

save_recording_path: str | None = None save_downloads_path: str | None = None trace_path: str | None = None locale: str | None = None user_agent: str = ( 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.102 Safari/537.36' )

highlight_elements: bool = True viewport_expansion: int = 500 allowed_domains: list[str] | None = None include_dynamic_attributes: bool = True

_force_keep_context_alive: bool = False ``` The _is_url_allowed() method is responsible for checking whether a given URL is permitted: ```python def _is_url_allowed(self, url: str) -> bool: """Check if a URL is allowed based on the whitelist configuration.""" if not self.config.allowed_domains: return True

try: from urllib.parse import urlparse

parsed_url = urlparse(url) domain = parsed_url.netloc.lower()

# Remove port number if present if ':' in domain: domain = domain.split(':')[0]

# Check if domain matches any allowed domain pattern return any( domain == allowed_domain.lower() or domain.endswith('.' + allowed_domain.lower()) for allowed_domain in self.config.allowed_domains ) except Exception as e: logger.error(f'Error checking URL allowlist: {str(e)}') return False ``` The core issue stems from the line `domain = domain.

split(':')[0]`, which allows an attacker to manipulate basic authentication credentials by providing a username:password pair. By replacing the username with a whitelisted domain, the check can be bypassed, even though the actual domain remains different. ### Proof of Concept (PoC)

Set allowed_domains to ['example.com'] and use the following URL:

https://example.com:pass@localhost:8080

This allows bypassing all whitelist controls and accessing restricted internal services. ### Impact

- Affected all users relying on this functionality for security. - Potential for unauthorized enumeration of localhost services and internal networks. - Ability to bypass domain whitelisting, leading to unauthorized browsing.

Affected package ranges reported by GitHub: browser-use: <= 0.1.44

Scores and how they were measured

CVSS base severity

9.3

Version 3.1As of

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L

Measurement source (opens a new tab)

How bad it is if exploited. Not a prediction of exploitation or proof you are exposed.

EPSS probability

Not available

A model's estimate of exploitation in the next 30 days, not certainty or your own risk.

Related technology

Sources

  1. Primary source

    GitHub-reviewed advisory GHSA-x39x-9qw5-ghrf (opens a new tab)

    The public advisory supplies the description, affected package/version ranges, and any listed CVSS metric. GitHub review is not local review.

    Published Checked

  2. Primary source

    GitHub public advisory API page (opens a new tab)

    The API page supplied GHSA-x39x-9qw5-ghrf, its actual identifiers, source dates, and structured metrics.

    Published Date not suppliedChecked

Cite this record

For factual claims, cite the primary sources above; cite KEVWire for its compilation, dates, and classifications.

APA

KEVWire. (2026, October 27). Browser Use allows bypassing `allowed_domains` by putting a decoy domain in http auth username portion of a URL (CVE-2025-47241). https://kevwire.com/record/CVE-2025-47241

MLA

"Browser Use allows bypassing `allowed_domains` by putting a decoy domain in http auth username portion of a URL (CVE-2025-47241)." KEVWire, 27 Oct. 2026, kevwire.com/record/CVE-2025-47241.

Chicago

KEVWire. "Browser Use allows bypassing `allowed_domains` by putting a decoy domain in http auth username portion of a URL (CVE-2025-47241)." Last modified October 27, 2026. https://kevwire.com/record/CVE-2025-47241.

Evidence summary (plain text)

Browser Use allows bypassing `allowed_domains` by putting a decoy domain in http auth username portion of a URL (May 5, 2025).
The `BrowserContextConfig` class defines an `allowed_domains` list, which is intended to limit accessible domains. This list is checked in the `_is_url_allowed()` method before navigation:

```python
@dataclass
class BrowserContextConfig:
 """
 [STRIPPED]
 """
 cookies_file: str | None = None
 minimum_wait_page_load_time: float = 0.5
 wait_for_network_idle_page_load_time: float = 1
 maximum_wait_page_load_time: float = 5
 wait_between_actions: float = 1
CVSS 9.3 (version 3.1; evidence as of Oct 27, 2026; https://github.com/advisories/GHSA-x39x-9qw5-ghrf).
Sources:
GitHub-reviewed advisory GHSA-x39x-9qw5-ghrf: https://github.com/advisories/GHSA-x39x-9qw5-ghrf
GitHub public advisory API page: https://api.github.com/advisories?type=reviewed&per_page=100&sort=updated&direction=desc
Record ID: CVE-2025-47241.
Record origin: Ingested record.
AI evidence: Not assessed.
Known exploitation: Not assessed.
Zero-day status: Not assessed. KEV membership alone does not establish zero-day status.
About this data

This record was ingested from a data source. Retrieved: Oct 27, 2026, 16:25 UTC. Ingestion is not an independent editorial investigation.

A CISA KEV listing documents known exploitation, not necessarily a zero-day; absence from the catalog does not prove a vulnerability has never been exploited.

Technology tags indicate possible relevance, not verified exposure. Confirm the affected product, version, and configuration against your own inventory; KEVWire does not scan your systems.

A personal reading checklist on this device, not verified remediation.

Record JSON

Your account

Email alerts

Email alerts are not available yet. To follow your stack today, use its RSS feed, which honors your filters, or connect an AI agent through the API.

Suggest an improvement

Ideas, missing sources, corrections, and bugs are all welcome. No account needed. Suggestions are reviewed by a person before anything changes.

Record details

Record detail