Description
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.
Published: 2026-10-08
Score: 9.8 Critical
EPSS: < 1% Very Low
KEV: No
Impact: Authentication/Authorization Bypass via Algorithm Confusion
Action: Patch ASAP
AI Analysis

Impact

This vulnerability allows an attacker to explain that the JWT library can incorrectly treat an RSA public key as an HMAC secret when the key text contains hidden non‑whitespace characters before the PEM header. The result is that the library falls back to HS256, an HMAC algorithm, for which the attacker can compute a signature using the public key bytes. The effect is that an attacker who knows the public key can forge arbitrary HS256 tokens and gain unauthorized authentication or authorization.

Affected Systems

The issue affects the package nearform:fast-jwt versions from 6.2.0 up through the last release before 6.3.0. The safe fix is to update to version 6.3.0 or later, which removes the fallback and enforces strict PEM detection.

Risk and Exploitability

The CVSS base score of 9.8 indicates critical severity. EPSS data is not available, so the exploitation probability is unknown, but the root cause is a severe algorithm confusion that is publicly known. The vulnerability is not listed in the CISA KEV catalog. Attackers would need to supply or obtain the public key and use the library’s signing function; an allowlist that permits only asymmetric algorithms eliminates the attack surface.

Generated by OpenCVE AI on October 8, 2026 at 23:27 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade fast-jwt to version 6.3.0 or newer to apply the patch that fixes algorithm confusion
  • Reconfigure JWT handling to allow only the intended asymmetric algorithms (e.g., RS256) and disable HS256 unless explicitly required
  • Validate all public key inputs to match strict PEM formatting, stripping any leading non‑whitespace characters or wrapper text before the PEM header

Generated by OpenCVE AI on October 8, 2026 at 23:27 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-ww5h-9m49-7xx4 fast-jwt: Incomplete patch of CVE-2026-34950: Non-whitespace key-prefix re-enables RSA→HS256 algorithm confusion
History

Tue, 13 Oct 2026 17:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

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


Fri, 09 Oct 2026 00:15:00 +0000

Type Values Removed Values Added
First Time appeared Nearform
Nearform fast-jwt
Vendors & Products Nearform
Nearform fast-jwt

Thu, 08 Oct 2026 22:00:00 +0000

Type Values Removed Values Added
Description 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.
Title fast-jwt: Incomplete patch of CVE-2026-34950: Non-whitespace key-prefix re-enables RSA→HS256 algorithm confusion
Weaknesses CWE-347
References
Metrics cvssV3_1

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


Subscriptions

Nearform Fast-jwt
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-10-13T16:26:25.790Z

Reserved: 2026-10-08T17:21:52.975Z

Link: CVE-2026-107722

cve-icon Vulnrichment

Updated: 2026-10-13T16:26:21.743Z

cve-icon NVD

Status : Deferred

Published: 2026-10-08T22:17:28.447

Modified: 2026-10-13T17:17:16.970

Link: CVE-2026-107722

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-09T00:00:09Z

Weaknesses
  • CWE-347

    Improper Verification of Cryptographic Signature