Nearform Fast-Jwt vulnerabilities
14 known vulnerabilities affecting nearform/fast-jwt.
Total CVEs
14
CISA KEV
0
Public exploits
0
Exploited in wild
0
Severity breakdown
CRITICAL4HIGH4MEDIUM6
Vulnerabilities
Page 1 of 1
CVE-2026-44351P2CRITICALCVSS 9.1fixed in 6.2.42026-05-13
CVE-2026-44351 [CRITICAL] CWE-287 CVE-2026-44351: fast-jwt provides fast JSON Web Token (JWT) implementation. Prior to 6.2.4, a critical authenticatio
fast-jwt provides fast JSON Web Token (JWT) implementation. Prior to 6.2.4, a critical authentication-bypass vulnerability in fast-jwt's async key-resolver flow allows any unauthenticated attacker to forge arbitrary JWTs that are accepted as authentic. When the application's key resolver returns an empty string (''), for example via the common key
ghsanvd
CVE-2026-107722P2CRITICALCVSS 9.8v>= 6.2.0, < 6.3.02026-10-08
CVE-2026-107722 [CRITICAL] CWE-347 CVE-2026-107722: fast-jwt provides fast JSON Web Token (JWT) implementation. From 6.2.0 until 6.3.0, fast-jwt can mis
fast-jwt provides fast JSON Web Token (JWT) implementation. From 6.2.0 until 6.3.0, fast-jwt can misclassify RSA public-key text as an HMAC secret when the key has non-whitespace content before its PEM header. In src/crypto.js, performDetectPublicKeyAlgorithms trims whitespace but publicKeyPemMatcher remains start-anchored, so comments, control
ghsanvd
CVE-2026-107723P3HIGHCVSS 8.1fixed in 6.3.02026-10-08
CVE-2026-107723 [HIGH] CWE-1287 CVE-2026-107723: fast-jwt provides fast JSON Web Token (JWT) implementation. Prior to 6.3.0, fast-jwt createVerifier
fast-jwt provides fast JSON Web Token (JWT) implementation. Prior to 6.3.0, fast-jwt createVerifier accepts a validly signed JWT whose payload is a JSON array because src/decoder.js checks that the payload is an object but does not reject arrays. The claim validator loop then finds no named exp, nbf, iss, aud, sub, jti, or nonce properties and silen
ghsanvd
CVE-2026-107720P3HIGHCVSS 7.4fixed in 6.3.12026-10-08
CVE-2026-107720 [HIGH] CWE-20 CVE-2026-107720: fast-jwt provides fast JSON Web Token (JWT) implementation. Prior to 6.3.1, fast-jwt createVerifier
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
nvd
CVE-2026-35039P3CRITICALCVSS 9.1≥ 0.1.0, < 6.1.0v>= 0.0.1, < 6.2.02026-04-06
CVE-2026-35039 [CRITICAL] CWE-345 CVE-2026-35039: fast-jwt provides fast JSON Web Token (JWT) implementation. From 0.0.1 to before 6.2.0, setting up a
fast-jwt provides fast JSON Web Token (JWT) implementation. From 0.0.1 to before 6.2.0, setting up a custom cacheKeyBuilder method which does not properly create unique keys for different tokens can lead to cache collisions. This could cause tokens to be mis-identified during the verification process leading to valid tokens returning claims from d
ghsanvdosv
CVE-2026-107724P3HIGHCVSS 7.4v>= 6.2.4, < 6.3.02026-10-08
CVE-2026-107724 [HIGH] CWE-347 CVE-2026-107724: fast-jwt provides fast JSON Web Token (JWT) implementation. In 6.2.4, fast-jwt can classify raw seri
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
ghsanvd
CVE-2026-34950P3CRITICALCVSS 9.1fixed in 6.2.02026-04-06
CVE-2026-34950 [CRITICAL] CVE-2026-34950: fast-jwt provides fast JSON Web Token (JWT) implementation. In 6.1.0 and earlier, the publicKeyPemMa
fast-jwt provides fast JSON Web Token (JWT) implementation. In 6.1.0 and earlier, the publicKeyPemMatcher regex in fast-jwt/src/crypto.js uses a ^ anchor that is defeated by any leading whitespace in the key string, re-enabling the exact same JWT algorithm confusion attack that CVE-2023-48223 patched.
ghsanvdosv
CVE-2026-35042P3HIGHCVSS 7.5fixed in 6.2.0≤ 6.1.02026-04-06
CVE-2026-35042 [HIGH] CWE-345 CVE-2026-35042: fast-jwt provides fast JSON Web Token (JWT) implementation. In 6.1.0 and earlier, fast-jwt does not
fast-jwt provides fast JSON Web Token (JWT) implementation. In 6.1.0 and earlier, fast-jwt does not validate the crit (Critical) Header Parameter defined in RFC 7515 §4.1.11. When a JWS token contains a crit array listing extensions that fast-jwt does not understand, the library accepts the token instead of rejecting it. This violates the MUST requirem
ghsanvdosv
CVE-2025-30144P3MEDIUMCVSS 6.5fixed in 5.0.62025-03-19
CVE-2025-30144 [MEDIUM] CWE-290 CVE-2025-30144: fast-jwt provides fast JSON Web Token (JWT) implementation. Prior to 5.0.6, the fast-jwt library doe
fast-jwt provides fast JSON Web Token (JWT) implementation. Prior to 5.0.6, the fast-jwt library does not properly validate the iss claim based on the RFC 7519. The iss (issuer) claim validation within the fast-jwt library permits an array of strings as a valid iss value. This design flaw enables a potential attack where a malicious actor crafts a J
ghsanvdosv
CVE-2026-35041P3MEDIUMCVSS 6.5≥ 5.0.0, < 6.2.1v>= 5.0.0, < 6.2.12026-04-09
CVE-2026-35041 [MEDIUM] CWE-1333 CVE-2026-35041: fast-jwt provides fast JSON Web Token (JWT) implementation. From 5.0.0 to 6.2.0, a denial-of-service
fast-jwt provides fast JSON Web Token (JWT) implementation. From 5.0.0 to 6.2.0, a denial-of-service condition exists in fast-jwt when the allowedAud verification option is configured using a regular expression. Because the aud claim is attacker-controlled and the library evaluates it against the supplied RegExp, a crafted JWT can trigger catastrop
ghsanvdosv
CVE-2023-48223P4MEDIUMCVSS 5.9fixed in 3.3.2≤ 6.1.02023-11-20
CVE-2023-48223 [MEDIUM] CWE-20 CVE-2023-48223: fast-jwt provides fast JSON Web Token (JWT) implementation. Prior to version 3.3.2, the fast-jwt lib
fast-jwt provides fast JSON Web Token (JWT) implementation. Prior to version 3.3.2, the fast-jwt library does not properly prevent JWT algorithm confusion for all public key types. The 'publicKeyPemMatcher' in 'fast-jwt/src/crypto.js' does not properly match all common PEM formats for public keys. To exploit this vulnerability, an attacker needs to c
ghsanvdosv
CVE-2026-107721P4MEDIUMCVSS 5.9fixed in 6.3.02026-10-08
CVE-2026-107721 [MEDIUM] CWE-613 CVE-2026-107721: fast-jwt provides fast JSON Web Token (JWT) implementation. Prior to 6.3.0, fast-jwt createVerifier
fast-jwt provides fast JSON Web Token (JWT) implementation. Prior to 6.3.0, fast-jwt createVerifier accepts Infinity for clockTolerance because its option validation checks type and negativity but not finiteness. In validateClaimDateValue, infinite positive and negative modifiers make exp and nbf comparisons always pass, allowing expired or not-yet
ghsanvd
CVE-2026-35040P4MEDIUMCVSS 5.3fixed in 6.2.12026-04-09
CVE-2026-35040 [MEDIUM] CWE-440 CVE-2026-35040: fast-jwt provides fast JSON Web Token (JWT) implementation. Prior to 6.2.1, using certain modifiers
fast-jwt provides fast JSON Web Token (JWT) implementation. Prior to 6.2.1, using certain modifiers on RegExp objects in the allowedAud, allowedIss, allowedSub, allowedJti, or allowedNonce options in verify functions can cause certain unintended behaviours. This is because some modifiers are stateful and will cause failures in every second verificati
ghsanvdosv
CVE-2026-107719P4MEDIUMCVSS 4.2fixed in 6.3.42026-10-08
CVE-2026-107719 [MEDIUM] CWE-613 CVE-2026-107719: fast-jwt provides fast JSON Web Token (JWT) implementation. Prior to 6.3.4, the fast-jwt createVerif
fast-jwt provides fast JSON Web Token (JWT) implementation. Prior to 6.3.4, the fast-jwt createVerifier cache can continue accepting a previously valid, signed JWT after its exp time when caching is enabled and the token has exp but no iat. In src/verifier.js, cacheSet derives the exp cache deadline only when iat is present, so the cache falls bac
ghsanvd