fast-jwt vulnerabilities

Browse known CVEs and advisories by package and ecosystem. Severity tells you the worst case. What determines real risk is whether the vulnerable code actually runs in your applications.

Get a demo

Browse by ecosystem

npmPyPIMavenGoRubyGemsCargoNuGetComposerpubSwiftGitHub Actions
CVE-IDSeverityPackage summary
CVE-2026-107719Mediumfast-jwt: fast-jwt: Verifier cache accepts expired JWTs without iat.CVE-2026-107720Highfast-jwt: fast-jwt: createVerifier accepts unsigned JWTs when key is '' or null and algorithms is explicitly setCVE-2026-107722Criticalfast-jwt: fast-jwt: Incomplete patch of CVE-2026-34950: Non-whitespace key-prefix re-enables RSA→HS256 algorithm confusionCVE-2026-107721Mediumfast-jwt: fast-jwt clockTolerance: Infinity silently bypasses both exp and nbf validation (and persists in the verifier cache)CVE-2026-107723Highfast-jwt: fast-jwt : Silent claim-validator bypass when JWT payload is a JSON arrayCVE-2026-107724Highfast-jwt: fast-jwt treats raw public JWK JSON as an HMAC secret, enabling HS256 token forgeryCVE-2026-44351Criticalfast-jwt: fast-jwt: JWT auth bypass due to empty HMAC secret accepted by async key resolverCVE-2026-35041Mediumfast-jwt: fast-jwt has a ReDoS when using RegExp in allowed* leading to CPU exhaustion during token verificationCVE-2026-35040Mediumfast-jwt: fast-jwt: Stateful RegExp (/g or /y) causes non-deterministic allowed-claim validation (logical DoS)CVE-2026-35042Highfast-jwt: fast-jwt accepts unknown `crit` header extensions (RFC 7515 violation)CVE-2026-35039Criticalfast-jwt: fast-jwt: Cache Confusion via cacheKeyBuilder Collisions Can Return Claims From a Different Token (Identity/Authorization Mixup)CVE-2026-34950Criticalfast-jwt: fast-jwt: Incomplete fix for CVE-2023-48223: JWT Algorithm Confusion via Whitespace-Prefixed RSA Public KeyCVE-2025-30144Mediumfast-jwt: Fast-JWT Improperly Validates iss ClaimsCVE-2023-48223Mediumfast-jwt: JWT Algorithm Confusion

Stop the waste.
Protect your environment with Kodem.