Evidence · DiggingBeagle record
Gemini CLI issue 30073: OAuth metadata fetches bypass safe dispatcher
The Gemini CLI issue identifies OAuth discovery and dynamic registration HTTP requests that do not use the same safe dispatcher as other MCP traffic, so a previously checked host may resolve differently at connection time.
- Source role
- primary disclosure
Evidence record
The Gemini CLI issue identifies OAuth discovery and dynamic registration HTTP requests that do not use the same safe dispatcher as other MCP traffic, so a previously checked host may resolve differently at connection time.
Claim-level citations (1)
- supportsGemini CLI MCP OAuth metadata requests may bypass safe network dispatch: The Gemini CLI issue identifies OAuth discovery and dynamic registration HTTP requests that do not use the same safe dispatcher as other MCP traffic, so a previously checked host may resolve differently at connection time.
Issue 30073, metadata and registration request paths, DNS validation mismatch