CVE-2026-107720

fast-jwt: createVerifier accepts unsigned JWTs when key is '' or null and algorithms is explicitly set

Published Oct 8, 2026 CVSS 3.1 · 7.4 High EPSS < 1% KEV · Not listed
Description
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 gate. An attacker can therefore submit a token containing arbitrary claims without possessing a signing key, resulting in authentication or authorization bypass. Claim validators still run, and non-empty keys, an empty key without algorithms, and the async key resolver path do not have this behavior. This issue is fixed in version 6.3.1.

Analysis

AI-generated

Technical impact

fast-jwt allows creation of verifiers that accept unsigned JWTs when the signing key is an empty string or null and an explicit algorithm list is provided. The bypass permits an attacker to include arbitrary claims in a token without possessing a signing key, leading to unauthorized access or privilege escalation. The flaw is rooted in improper input validation and failure to enforce signature checks (CWE-20, CWE-347).

Affected Systems

any deployment of the nearform fast-jwt library before version 6.3.1 is affected. The issue is addressed in the 6.3.1 release and newer. If an application relies on older versions and does not enforce signed tokens, it remains vulnerable.

Risk and Exploitability

The CVSS score of 7.4 indicates high severity. EPSS is not available, but the vulnerability is not yet listed in the KEV catalog, suggesting no known widespread exploitation yet. The likely attack vector is over any network channel that delivers tokens to the verifier, such as HTTP or other IPC mechanisms – this is inferred from the description, which states that an attacker can submit a token containing arbitrary claims. The attack does not require privileged knowledge of a secret key, making it straightforward for malicious actors to subvert authentication or authorization.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade fast-jwt to version 6.3.1 or later.
  • If upgrading is not possible, ensure that any verifier creation uses a non‑empty key and omits algorithm allowlists, or switch to the asynchronous key resolver path.
  • Add a server‑side check to reject unsigned tokens or those missing a signature before processing claims.

Generated by OpenCVE AI on October 9, 2026 at 00:03 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-8wpc-h4q6-8fxv fast-jwt: createVerifier accepts unsigned JWTs when key is '' or null and algorithms is explicitly set
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Nearform
Nearform fast-jwt
Vendors & Products Nearform
Nearform fast-jwt
Type Values Removed Values Added
Description 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 gate. An attacker can therefore submit a token containing arbitrary claims without possessing a signing key, resulting in authentication or authorization bypass. Claim validators still run, and non-empty keys, an empty key without algorithms, and the async key resolver path do not have this behavior. This issue is fixed in version 6.3.1.
Title fast-jwt: createVerifier accepts unsigned JWTs when key is '' or null and algorithms is explicitly set
Weaknesses CWE-20
CWE-347
References
Metrics cvssV3_1

{'score': 7.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N'}

Weaknesses
  • CWE-20

    Improper Input Validation

  • CWE-347

    Improper Verification of Cryptographic Signature

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 9, 2026, 2:32 PM
Reserved
Oct 8, 2026, 5:21 PM
Status
Deferred
Published
Oct 8, 2026, 10:17 PM
Modified
Oct 9, 2026, 3:17 PM