CVE-2026-107724
fast-jwt provides fast JSON Web Token (JWT) implementation. In …
fast-jwt provides fast JSON Web Token (JWT) implementation. In 6.2.4, fast-jwt can classify raw serialized public JWK or JWKS JSON as an HMAC secret because src/crypto.js performDetectPublicKeyAlgorithms treats non-PEM strings as symmetric key material. If HS256 is explicitly allowed or inferred, an attacker who knows the exact serialized public-key bytes can use those bytes as an HMAC key and create a token containing arbitrary claims that createVerifier accepts. Serialization ordering or whitespace differences can prevent exploitation, and applications using supported PEM keys with an asymmetric-only algorithm allowlist are not affected. This issue is fixed in version 6.3.0.
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/10f9591349199ed2ab9fa1748ce92cdca697f6cf
- github.com/nearform/fast-jwt/pull/636
- github.com/nearform/fast-jwt/releases/tag/v6.3.0
- github.com/nearform/fast-jwt/security/advisories/GHSA-g3jj-5cmm-3hxx
- github.com/advisories/GHSA-g3jj-5cmm-3hxx
- nvd.nist.gov/vuln/detail/CVE-2026-107724
- cve.org/CVERecord?id=CVE-2026-107724
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.