JWT alg none
What a jwt-alg-none finding of fallow security means, why it matters and how to fix it.
What it reports
Catalogue security candidate for CWE-347.
Security explains how fallow finds it.
Why it matters
A token signed with none has no signature. Anyone can change its claims, and a verifier that accepts none treats the token as valid.
Example
jwt.sign(payload, '', { algorithm: 'none' });
Fix
Review the candidate trace before acting. Confirm attacker control, missing sanitization, and reachable runtime context, then fix with the category-appropriate safer API or add a reviewed suppression.
Facts
| Fact | Value |
|---|---|
| Issue type | jwt-alg-none |
| Rule id in SARIF output | security/jwt-alg-none |
| Command | fallow security |
| Default severity | off |
| Suppression comment | // fallow-ignore-next-line security-sink |
Fixable with fallow fix | No |
| Opt-in | Yes |
Note. Tainted-sink catalogue category; the security-sink suppression token covers every category.