CVE-2026-107720
fast-jwt provides fast JSON Web Token (JWT) implementation. Prior …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/nearform/fast-jwt/commit/e22a151e83bf6d5e54e281216982d204d5665534
- github.com/nearform/fast-jwt/pull/649
- github.com/nearform/fast-jwt/releases/tag/v6.3.1
- github.com/nearform/fast-jwt/security/advisories/GHSA-8wpc-h4q6-8fxv
- github.com/advisories/GHSA-8wpc-h4q6-8fxv
- nvd.nist.gov/vuln/detail/CVE-2026-107720
- cve.org/CVERecord?id=CVE-2026-107720
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.