ChatGPT silently passes data between connectors and the bounty wants an ID card
First seen by Oriel on .
AI summary
A forum report describes ChatGPT silently switching connectors between confirmation and follow-up MCP tool calls, potentially crossing OAuth authorization boundaries without user awareness.
- Connector A initiated a confirmation flow, but ChatGPT routed the follow-up call through Connector B, which used a separate OAuth client for the same MCP server.
- The one-time confirmation code generated by Connector A’s widget was sent through ui/message and rejected when redeemed through Connector B because it was client-bound.
- The report argues that connector identity, rather than the shared MCP server URL, defines the authorization boundary across tenants, partners, environments, or providers.
- Suggested safeguards include preserving the originating connector, preventing automatic switching, requiring approval for changes, validating operation and client identity, and logging routing decisions.
- The reporter says they declined the bug bounty process because it required personal information, including biometric identification and an ID card, before submission.
#mcp #oauth #tool calling #authorization
Generated by gpt-5.6-sol. Check the original for details.
Metric trends
Last 30 days · Up to 120 recorded samples per source and metric, with reposts kept separate · First and latest retained
Points
Score reported by the source.
- Hacker News: 91, latest observation ; +74 over observed period since
Comments
Comment count reported by the source.
- Hacker News: 38, latest observation ; +35 over observed period since
Aliases
| Source | External ID | URL |
|---|---|---|
| Hacker News | 50399569 | https://community.openai.com/t/security-follow-up-tool-call-silently-routed-to-a-different-connector/1413053 Read discussion |