CVE-2026-34950: CWE-327: Use of a Broken or Risky Cryptographic Algorithm in nearform fast-jwt
CVE-2026-34950 is a critical vulnerability in nearform's fast-jwt library versions 6. 1. 0 and earlier. The issue arises because the publicKeyPemMatcher regex in the crypto. js file uses a start-of-string anchor (^) that can be bypassed by leading whitespace in the key string. This flaw reintroduces a previously patched JWT algorithm confusion attack (CVE-2023-48223). The vulnerability allows an attacker to exploit the use of a broken or risky cryptographic algorithm, potentially leading to full compromise of JWT validation. No official patch or remediation guidance is currently available from the vendor.
AI Analysis
Technical Summary
The fast-jwt library provides a fast JSON Web Token implementation. In versions 6.1.0 and earlier, the regex used to match public keys (publicKeyPemMatcher in fast-jwt/src/crypto.js) relies on a ^ anchor that fails to account for leading whitespace in the key string. This weakness defeats the regex's intended validation, effectively re-enabling the JWT algorithm confusion attack that was previously addressed in CVE-2023-48223. The vulnerability is classified under CWE-327, indicating the use of a broken or risky cryptographic algorithm. The CVSS v3.1 base score is 9.1 (critical), reflecting network attack vector, low attack complexity, no privileges or user interaction required, and high confidentiality and integrity impact.
Potential Impact
Successful exploitation of this vulnerability could allow attackers to bypass JWT signature verification by exploiting algorithm confusion, leading to unauthorized access or privilege escalation in systems relying on fast-jwt for authentication. The impact includes full compromise of confidentiality and integrity of JWT-based authentication tokens. There are no known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official fix or patch links are provided, users should monitor nearform's official channels for updates. As a temporary measure, avoid using affected versions (<= 6.1.0) of fast-jwt in production environments or implement additional validation layers for JWT processing to mitigate algorithm confusion risks.
CVE-2026-34950: CWE-327: Use of a Broken or Risky Cryptographic Algorithm in nearform fast-jwt
Description
CVE-2026-34950 is a critical vulnerability in nearform's fast-jwt library versions 6. 1. 0 and earlier. The issue arises because the publicKeyPemMatcher regex in the crypto. js file uses a start-of-string anchor (^) that can be bypassed by leading whitespace in the key string. This flaw reintroduces a previously patched JWT algorithm confusion attack (CVE-2023-48223). The vulnerability allows an attacker to exploit the use of a broken or risky cryptographic algorithm, potentially leading to full compromise of JWT validation. No official patch or remediation guidance is currently available from the vendor.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The fast-jwt library provides a fast JSON Web Token implementation. In versions 6.1.0 and earlier, the regex used to match public keys (publicKeyPemMatcher in fast-jwt/src/crypto.js) relies on a ^ anchor that fails to account for leading whitespace in the key string. This weakness defeats the regex's intended validation, effectively re-enabling the JWT algorithm confusion attack that was previously addressed in CVE-2023-48223. The vulnerability is classified under CWE-327, indicating the use of a broken or risky cryptographic algorithm. The CVSS v3.1 base score is 9.1 (critical), reflecting network attack vector, low attack complexity, no privileges or user interaction required, and high confidentiality and integrity impact.
Potential Impact
Successful exploitation of this vulnerability could allow attackers to bypass JWT signature verification by exploiting algorithm confusion, leading to unauthorized access or privilege escalation in systems relying on fast-jwt for authentication. The impact includes full compromise of confidentiality and integrity of JWT-based authentication tokens. There are no known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official fix or patch links are provided, users should monitor nearform's official channels for updates. As a temporary measure, avoid using affected versions (<= 6.1.0) of fast-jwt in production environments or implement additional validation layers for JWT processing to mitigate algorithm confusion risks.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-31T17:27:08.661Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69d3dc220a160ebd92c52bd4
Added to database: 4/6/2026, 4:15:30 PM
Last enriched: 4/6/2026, 4:30:30 PM
Last updated: 4/6/2026, 5:36:00 PM
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.