Nearform fast-jwt
fast-jwt: createVerifier accepts unsigned JWTs when key is '' or null and algorithms is explicitly set
fast-jwt provides fast JSON Web Token (JWT) implementation. Prior to 6.3.1, fast-jwt createVerifier accepts an unsigned JWT when key is an empty string or null and algorithms is a non-empty allowlist. Falsy synchronous keys bypass prepareKeyOrSecret, allowedAlgorithms remains active, hasKey is false, and the empty signature avoids the verifySignature gate. An attacker can therefore submit a token containing arbitrary claims without possessing a signing key, resulting in authentication or authorization bypass. Claim validators still run, and non-empty keys, an empty key without algorithms, and the async key resolver path do not have this behavior. This issue is fixed in version 6.3.1.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 6.3.1
Fixed in 6.3.1
Mitigation
Upgrade fast-jwt to 6.3.1 or later.
References
- Vendor advisory github.com/nearform/fast-jwt/security/advisori…
- Patch github.com/nearform/fast-jwt/pull/649
- Patch github.com/nearform/fast-jwt/commit/e22a151e83…
1 more
- Release notes github.com/nearform/fast-jwt/releases/tag/v6.3…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.1 pending
Pending 1
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| federiconbaez/cortex9-fastjwt-empty-key-unsigned-accept-model | 9 Nov 2026 +32 d | 14 Nov 2026 | 0 | Pending
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.