CVE-2026-44699

LibJWT: Algorithm confusion allows JWT forgery with RSA JWK as empty-key HMAC

State
Published
Severity
9.1 Critical
Published
May 15, 2026
Updated
May 15, 2026
Reserved
May 7, 2026

Read the record on cve.org

Description

LibJWT is a C JSON Web Token Library. From 3.0.0 to 3.3.2, libjwt accepts an RSA JWK that does not contain an alg parameter as the verification key for an HS256/HS384/HS512 token. In the OpenSSL backend, this causes HMAC verification to run with a zero-length key, so an attacker can forge a valid JWT without knowing any secret or RSA private key. This is an algorithm-confusion authentication bypass. It affects applications that load RSA keys from JWKS where alg is omitted, which is valid JWK syntax and common in real deployments, and then choose the verification algorithm from the JWT header, for example in a kid lookup callback. This vulnerability is fixed in 3.3.3.

Scores

CVSSScoreVectorSource
4.09.1 CriticalCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NGitHub_M

Weaknesses

  • CWE-327 Use of a Broken or Risky Cryptographic Algorithm
  • CWE-347 Improper Verification of Cryptographic Signature

Affected Products

ProductVersions
libjwtbenmcollins
  • >= 3.0.0, < 3.3.3Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.