JWT verify missing algorithms allowlist
What a jwt-verify-missing-algorithms 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
Without an algorithms allowlist, the token header chooses the algorithm. An attacker can then pick an algorithm that lets them forge a valid token.
Example
jwt.verify(token, publicKey, { audience: 'api' });
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-verify-missing-algorithms |
| Rule id in SARIF output | security/jwt-verify-missing-algorithms |
| 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.