The vulnerability allows an attacker to reuse an OAuth token obtained for one MCP server to access another MCP server. This is possible because the access tokens were not correctly bound to the specific server (resource) they were issued for. The root cause lies in the OAuthProxy.__init__ method, which configured the JWT issuer with a generic audience claim based on the server's base_url instead of its specific resource URL. This misconfiguration is exploited through the OAuthProxy.authorize method, which, in its vulnerable state, failed to validate the resource parameter in the incoming authorization request. An attacker could therefore trick a user into authorizing with a malicious server, steal the resulting token, and use it on a legitimate server because the token's audience was not specific enough to be rejected. The patch addresses this by deferring the JWT issuer's configuration until the correct resource URL is known and by adding a strict resource validation check in the authorize method.