CVE-2026-90474: Client authentication bypass in MCPHub's built-in OAuth 2.0 authorization server
The built-in OAuth 2.0 authorization server in MCPHub versions before 1.0.32 has a client authentication bypass: an attacker can pass client validation at the token endpoint without providing client_secret and code_verifier. The authors traced this to requireClientSecret defaulting to false in mcp_settings.json, which makes node-oauth2-server skip the client_secret check, while MCPHub's own getClient validation also only executes when the request carries a client_secret; therefore, if an attacker obtains an authorization code via CSRF or other means, they can impersonate a client to exchange for an access token and access the victim's resources. The patch requires public clients without a client_secret to provide an S256 code_challenge in the authorization request, and enforces validation of client_secret and PKCE in the token request.