An SSRF (Server-Side Request Forgery) protection bypass exists during the OAuth2 credential authorization-code-to-access-token exchange. While OAuth2 discovery and dynamic-client-registration requests utilize a protected HTTP client, the token exchange process employs a separate client lacking SSRF guards. A user with credential-creation permissions can configure the access-token URL to point to an internal address. By completing the OAuth2 flow, the system sends a fixed-shape token-exchange POST request to the target and reflects the response body back to the attacker.