Which scenario describes the risk when a JWT signing key is weak or signing algorithm is insecure?

• A. The issuer uses a symmetric key with HS256
• B. The issuer uses a trusted key with RS256
• C. A weak signing key or algorithm is used that can be forged
• D. The token has no audience claim

Answer: (C)

The essential idea is that the ability to trust a JWT rests on its signature, which proves the token was created with the legitimate signing key and hasn’t been altered. When the signing key is weak or the algorithm used is insecure, an attacker can generate a forged signature that validates as if it came from the legitimate issuer. That means the attacker can create tokens that grant access they shouldn’t have, bypassing authentication and authorization controls.

If you’re using a symmetric key with HS256, the same secret signs and verifies the token. A weak or exposed secret makes it feasible for someone else to sign their own tokens. If you’re using an asymmetric setup like RS256, the private key signs and the public key verifies; again, if the private key is weak or compromised, forging becomes possible. The core risk is the ability to produce a valid signature for arbitrary payloads.

So the scenario that best describes this risk is one where a weak signing key or insecure signing algorithm is used, enabling forgery of tokens. Strong, properly managed keys and robust signing algorithms, along with correct validation (and rejecting weak or none algorithms), mitigate this risk.

Other configurations that involve robust keys and sound algorithms do not exhibit this forgery risk, and issues like missing audience claims pertain to token scope rather than the ability to forge a signature.