CVE-2026-44699

The record

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.

Affected packages

Related vulnerabilities

• CVE-2026-81822 The vulnerability, if exploited, could allow a miscreant with read access to PIMBoards… CWE-327
• CVE-2026-16693 IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to obtain… CWE-327
• CVE-2026-81859 CP4BA - IBM Enterprise Records could allow a local attacker to obtain sensitive… CWE-327
• CVE-2026-76133 The affected Ebyte product uses a deprecated hashing algorithm in an… CWE-327
• CVE-2026-39944 Ceph is an open-source distributed storage platform providing object, block, and file… CWE-327
• CVE-2026-78236 An insecure PIN derivation mechanism in ABR allows a low-privileged user to escalate… CWE-327
• CVE-2026-74888 openssl_encrypt versions before 1.4.0 use a non-standard PBKDF2 key derivation… CWE-327
• CVE-2026-27871 Cwe-327 Use of a Broken or Risky Cryptographic Algorithm vulnerability in Johnson… CWE-327