CVE-2026-35040
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 verification attempt regardless of the validity of the token provided. Such modifiers are /g (global matching) and /y (sticky matching). This does NOT allow invalid tokens to be accepted, only for valid tokens to be improperly rejected in some configurations. Instead it causes 50% of valid authentication requests to fail in an alternating pattern. This vulnerability is fixed in 6.2.1.
Scoring
- Severity
- MEDIUM
- CVSS base score
- 5.3
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- EPSS probability
- 0.38%
- CWE
- CWE-697, CWE-440
- Published
- 2026-04-09
- Last modified
- 2026-04-13
Affected products
- nearform fast-jwt
Weakness type
Related vulnerabilities
- CVE-2026-56101 — OpenBSD ieee80211_crypto_tkip.c TKIP MIC Countermeasure Logic Inversion DoS
- CVE-2026-73309 — XenForo < 2.3.13 Authentication Bypass via OAuth2 Token Endpoint
- CVE-2026-80227 — SQL string_trim removes only spaces, diverging from in-memory trimming in AshSql
- CVE-2026-18664 — Wrong interpretation of ACL ranges
- CVE-2026-73258 — Mongoose: Multipart boundary/header scan logic error in mg_http_next_multipart
- CVE-2026-75110 — MemOS Authentication Bypass via Unset INTERNAL_SERVICE_SECRET
- CVE-2026-50029 — js-toml has silent type confusion via falsy-primitive duplicate-key bypass
- CVE-2026-20765 — Incorrect comparison for some Intel(R) TDX Guest software before version 0.3.1 within Ring 3: User...