The `buildURL()` function fails to properly validate source strings when they begin with the same scheme as the base, such as http or https. This occurs because the WHATWG URL parser drops the scheme and resolves the remainder as a relative path. An attacker can use a payload that combines the scheme with a percent-encoded parent-directory sequence to bypass security checks. If the upstream server percent-decodes the request path before resolving dot-segments, an unauthenticated client can escape the configured prefix to access sibling or parent upstream endpoints, bypassing Fastify route guards.