CVE-2026-53939CWE-321CWE-330

CVE-2026-53939

Critical · published September 9, 2026

CVSS v3.1
9.1
EPSS
0%
Percentile
14.9
In the wild
Unconfirmed
What it is

OpenIDC/cjose is a C library implementing the Javascript Object Signing and Encryption (JOSE). In versions 0.6.1 through 0.6.2.5, when cjose encrypts a JWE using an AES-CBC-HMAC content-encryption algorithm (`A128CBC-HS256`, `A192CBC-HS384`, or `A256CBC-HS512`) together with any key-management algorithm that generates a fresh content-encryption key (CEK), the CEK is all zero bytes instead of being randomly generated. The resulting JWE is therefore encrypted and authenticated under a fixed, publicly known key, so anyone who obtains the JWE can recover the plaintext and forge or modify the content. This is fixed in version 0.6.2.6 by `_cjose_jwe_set_cek_aes_cbc()` generating the CEK from `RAND_bytes`. A regression test asserts that the `encrypted_key` differs across two encryptions for each AES-CBC-HMAC variant. Until upgrading, for data encrypted with cjose, three options are available. Use an AES-GCM `enc` (`A128GCM` / `A192GCM` / `A256GCM`) instead of an AES-CBC-HMAC `enc`, use `alg=dir` with a caller-supplied CEK, or avoid using cjose for JWE encryption with the affected algorithm pair. These are mitigations for new ciphertexts only; data already encrypted under the zero key remains compromised and should be re-encrypted (and any secrets it contained rotated).

The record
Technical detail
CVSS v3.1
9.1 · CRITICAL
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CVSS v4.0
Not supplied
EPSS
0.00245 · 14.9th percentile
Weaknesses
CWE-321 · Use of Hard-coded Cryptographic Key; CWE-330 · Use of Insufficiently Random Values
Published
2026-09-09T04:17Z
References (4)
EPSS history
Timeline
  • 10 SEP 03:17Z
    EPSS moved — → 0%
    epss
  • 08 SEP 23:36Z
    OpenIDC/cjose uses all-zero Content Encryption Key for AES-CBC-HMAC JWE encryption
    cvelistv5