---
answer: direct
beat: dev-practices
source: 1 article · updated: November 17, 2026
---

What's the actual security flaw people mean when they say JWT is risky?

JWT is a container format that supports many possible signing algorithms — including 'none', meaning no signature verification at all — and leaves the choice of algorithm to the implementer, decoded from a header the token itself carries. Historical vulnerabilities exploited this flexibility: forging a token with alg set to 'none', or tricking a server into verifying an RS256-signed token's signature using its own public key as if it were an HS256 secret. The JWT specification isn't broken; the amount of implementation choice it leaves open is what caused real vulnerabilities.

Answered in

JWT's Real Problem Was Never the Idea, It Was the Choices It Allows

JWT lets you choose 'none' as a signing algorithm. PASETO doesn't let you choose at all — versioned, fixed cipher suites instead of a menu of footguns.

Crashtech Editorial November 17, 2026 Development Best Practices

Read the full analysis

Other questions this article answers

More development best practices questions

Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the Development Best Practices beat.