auth login <url> should confirm before running well-known auth.command #10939

Activity

1. github-actions

   assigned

   thdxr

   on Jan 28, 2026
2. github-actions

   added

   windows

   on Jan 28, 2026
3. github-actions commented on Jan 28, 2026

   

   github-actionsBot

   on Jan 28, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • No trusted workspace functionality leads to arbitrary commands execution on startup #6361: No trusted workspace functionality leads to arbitrary commands execution on startup
   • All MCP oauth flow return potential CSRF attack #9510: All MCP oauth flow return potential CSRF attack

   Feel free to ignore if none of these address your specific case.
4. MaxMiksa commented on Jan 28, 2026

   

   MaxMiksa

   on Jan 28, 2026

   ContributorAuthor

   More actions

   Thanks — this is related in theme but a different (narrower) surface.

   This report is specifically about opencode auth login <url> (well-known providers) fetching <url>/.well-known/opencode and immediately executing the returned auth.command to obtain a token.

   It’s not about startup-time command execution; it’s a user-invoked login flow. The proposed change is minimal: validate the payload shape and require an explicit confirmation before running the remote-provided command (with --yes as an explicit automation bypass).
5. github-actions commented on Mar 30, 2026

   

   github-actionsBot

   on Mar 30, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.

   👎React with 👎4Reacted by Tv, Jonas Strehle, Magnus Bergmark and Cleroth

   😄React with 😄2Reacted by George Thomas and Cleroth
6. github-actions

   closed this as completedon Mar 30, 2026
7. tmccombs commented on Apr 3, 2026

   

   tmccombs

   on Apr 3, 2026

   More actions

   This seems like a pretty big security problem, is anything being done to address it?

   👍React with 👍2Reacted by Standa Lukeš and Magnus Bergmark
8. exyi commented on Apr 12, 2026

   

   exyi

   on Apr 12, 2026

   More actions

   Re-submitted as the stalebot requested: #22191

   👍React with 👍1Reacted by cryptoluks
9. malamama035-sudo commented on Sep 11, 2026

   

   malamama035-sudo

   on Sep 11, 2026

   More actions

   Description

   opencode auth login <url> fetches <url>/.well-known/opencode and runs the returned auth.command immediately to obtain a token.

   This executes a remote-provided command without an explicit confirmation step and without validating the payload shape.

   Suggested fix

   • Validate the well-known payload (require non-empty auth.command: string[] and auth.env: string).
   • Show the full command and require confirmation before running it.
   • Provide an explicit bypass flag for automation (e.g. --yes).

   Steps to reproduce

   1. Host a .well-known/opencode response with auth.command.
   2. Run: opencode auth login <url>.
   3. Observe the command executes immediately.

   Environment

   • OS: Windows 11
   • Terminal: Windows Terminal