Security pattern / case archive

JWT Signature Verification Bypass

A server accepts JWT claims without requiring a valid signature, allowing a client to alter trusted identity or authorization data.

Common discovery signals
  • A signed lower-privilege JWT is rejected by a protected route, while an unsigned token with changed claims reaches it.
  • A token using alg none and an empty signature is accepted as an authenticated session.
Safe validation approach

Keep the original session as a control, change only the minimum authorization claim, test one protected read-only route, and redact both token values from public evidence.

Related classifications

Related entries

Archive connections

Connected case files

01 record
CASE-019WEBVERSE
Connected evidence

ShippedSharp

JWT Signature Bypass / AI Tool SQL Injection

A member JWT was rejected by /admin, but the same claims with alg none and role admin opened the manager console. The report tool then accepted a controlled UNION query that reached one internal configuration value.