The vulnerability stems from improper JWT type validation in lifecycle endpoints. Key authentication functions like JwtAuthenticationFilter.attemptAuthentication would process malicious context JWTs without proper server-to-server checks. The JwtVerification class's verify method would be invoked during this process, lacking QSH claim validation specific to context JWTs. These functions appear in stack traces when processing installation events, making them visible in runtime profilers during exploitation. The high confidence for JwtAuthenticationFilter comes from its central role in authentication flow, while JwtVerification has medium confidence due to indirect evidence from community code examples.