Skip to main content
CriticalCodeOWASP A02:2021CWE-347

How to fix: JWT verifier allows alg: none

jwt.verify(token, secret, { algorithms: ['none'] }) explicitly allows the 'none' algorithm, so an attacker can send a token with alg:none and no signature and have it accepted.

Why it matters

Tokens are accepted without signatures or with a key the attacker controls, granting impersonation.

The `code-jwt-none-algorithm` check verifies that the server does not expose the `jwt-none-algorithm` weakness in the code category. The detection runs against the response headers, body, or auxiliary probes (DNS, TLS, async fetch) as appropriate.

How to fix it

  1. 1Always set algorithms explicitly: { algorithms: ['HS256'] } or ['RS256'].
  2. 2Reject any token whose header.alg differs from the expected list.
  3. 3Use jose or PyJWT >= 2.4 which enforce algorithms by default.

Code examples

Reject alg:none in JWT verification

TypeScript
import { jwtVerify } from "jose";

const secret = new TextEncoder().encode(process.env.JWT_SECRET!);

// jose library rejects alg:none by default when you pass a key
const { payload } = await jwtVerify(token, secret, {
  algorithms: ["HS256"], // explicit allowlist: rejects "none", "RS256", etc.
});

References

Detected automatically by VulnRadar. The check id is code-jwt-none-algorithm, stable across every scan so you can filter or diff on it.

See every code check

Questions

How severe is JWT verifier allows alg: none?
VulnRadar rates this critical severity in the code category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id code-jwt-none-algorithm, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does JWT verifier allows alg: none map to?
It maps to CWE-347. In the OWASP Top 10 it falls under A02:2021.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for jwt verifier allows alg: none

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: JWT verifier allows alg: none | VulnRadar