fix: prevent command injection in example URL opening#2082
Merged
Conversation
Comment on lines
128
to
129
| if parsed.scheme.lower() not in ALLOWED_SCHEMES: | ||
| print(f"Refusing to open URL with unsupported scheme '{parsed.scheme}': {url}") |
Contributor
There was a problem hiding this comment.
should this throw e.g. a ValueError instead of just printing?
Contributor
Author
There was a problem hiding this comment.
yea moved out of here into the handle elicitation function
90b1aa0 to
c516b8b
Compare
Kludex
reviewed
Feb 18, 2026
| @@ -124,12 +132,7 @@ def extract_domain(url: str) -> str: | |||
| def open_browser(url: str) -> None: | |||
Contributor
Author
There was a problem hiding this comment.
Yea not really, will remove.
Replace platform-specific subprocess calls with webbrowser.open() and add URL scheme validation to the elicitation example client. The previous Windows code path used shell=True with subprocess, which allowed command injection via crafted URLs containing shell metacharacters (e.g., & as a command separator in cmd.exe). Changes: - Remove subprocess/sys imports, use webbrowser.open() for all platforms - Add URL scheme allowlist (http/https only) in handle_url_elicitation, validated before prompting the user for consent - Return ElicitResult(action='decline') for disallowed schemes instead of silently continuing with action='accept' - Simplify open_browser() to a pure browser-opening helper - Align with the safe pattern already used in the OAuth example client
c516b8b to
591d4d9
Compare
Kludex
approved these changes
Feb 18, 2026
maxisbey
added a commit
that referenced
this pull request
Feb 18, 2026
Backport of #2082 to v1.x. Replace platform-specific subprocess calls with webbrowser.open() and add URL scheme validation (http/https allowlist) to block dangerous protocol handlers in the URL elicitation example client.
This was referenced Feb 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fix a command injection issue in the URL elicitation example client (
examples/snippets/clients/url_elicitation_client.py).Problem
The
open_browser()function usedsubprocess.run(["start", url], shell=True)on Windows, which allows shell metacharacter injection via crafted URLs. A malicious MCP server could send a URL likehttps://example.com/?state=abc&calcduring URL elicitation, andcmd.exewould interpret&as a command separator, executingcalc(or any arbitrary command).Fix
subprocesscalls withwebbrowser.open(), which handles cross-platform browser opening safely without shell invocationhttp,https) before prompting the user, returningElicitResult(action="decline")for disallowed schemesopen_browser()to a pure browser-opening helpersubprocessandsysimportsThis aligns with the safe pattern already used in
examples/clients/simple-auth-client/mcp_simple_auth_client/main.py.AI Disclaimer