The affected component is the Gravitee Management API authentication path. The application configuration reads jwt.secret and passes it to TokenAuthenticationFilter; the shipped configuration contains a known default, and the implementation logs a warning that the default can be used to impersonate anyone. An attacker who can reach the Management API and knows an existing user ID can create a forged HS256 JWT with its subject set to that identity, then submit it as a bearer token. The server can consequently process the request as the selected user without valid credentials. The normalized record specifies that the network attack requires no prior privileges or user interaction, but characterizes attack complexity as high; the evidence does not document why. The available evidence does not establish whether every deployment mode in scope has identical behavior, and it does not identify an exact fixed release.