Nearform fast-jwt
fast-jwt: Incomplete patch of CVE-2026-34950: Non-whitespace key-prefix re-enables RSA→HS256 algorithm confusion
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 characters, zero-width characters, or wrapper text can prevent PEM detection and reach the HMAC fallback. An attacker who knows the public key bytes can sign arbitrary HS256 claims with that public material when HS256 is inferred or allowed, resulting in authentication or authorization bypass. An asymmetric-only algorithm allowlist prevents the attack. This issue is fixed in version 6.3.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 6.2.0, < 6.3.0
Fixed in 6.3.0
Mitigation
Upgrade fast-jwt to 6.3.0 or later.
References
- Vendor advisory github.com/nearform/fast-jwt/security/advisori…
- Patch github.com/nearform/fast-jwt/pull/632
- Patch github.com/nearform/fast-jwt/commit/d96bbc6c53…
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.No PoC repositories found yet.