Red Hat Security Advisory: cjose security update
🔗 CVE IDs covered (1)
📋 Description
CVE-2026-53939 — cjose: OpenIDC/cjose uses all-zero Content Encryption Key for AES-CBC-HMAC JWE encryption
🎯 Affected products27
- Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- Red Hat Enterprise Linux CodeReady Linux Builder EUS (v. 10.0)
- cjose-0:0.6.2.2-7.el10_0.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- cjose-0:0.6.2.2-7.el10_0.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- cjose-0:0.6.2.2-7.el10_0.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- cjose-0:0.6.2.2-7.el10_0.2.src as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- cjose-0:0.6.2.2-7.el10_0.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- cjose-debuginfo-0:0.6.2.2-7.el10_0.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- cjose-debuginfo-0:0.6.2.2-7.el10_0.2.aarch64 as a component of Red Hat Enterprise Linux CodeReady Linux Builder EUS (v. 10.0)
- cjose-debuginfo-0:0.6.2.2-7.el10_0.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- cjose-debuginfo-0:0.6.2.2-7.el10_0.2.ppc64le as a component of Red Hat Enterprise Linux CodeReady Linux Builder EUS (v. 10.0)
- cjose-debuginfo-0:0.6.2.2-7.el10_0.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- cjose-debuginfo-0:0.6.2.2-7.el10_0.2.s390x as a component of Red Hat Enterprise Linux CodeReady Linux Builder EUS (v. 10.0)
- cjose-debuginfo-0:0.6.2.2-7.el10_0.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- cjose-debuginfo-0:0.6.2.2-7.el10_0.2.x86_64 as a component of Red Hat Enterprise Linux CodeReady Linux Builder EUS (v. 10.0)
- cjose-debugsource-0:0.6.2.2-7.el10_0.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- cjose-debugsource-0:0.6.2.2-7.el10_0.2.aarch64 as a component of Red Hat Enterprise Linux CodeReady Linux Builder EUS (v. 10.0)
- cjose-debugsource-0:0.6.2.2-7.el10_0.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- cjose-debugsource-0:0.6.2.2-7.el10_0.2.ppc64le as a component of Red Hat Enterprise Linux CodeReady Linux Builder EUS (v. 10.0)
- cjose-debugsource-0:0.6.2.2-7.el10_0.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- cjose-debugsource-0:0.6.2.2-7.el10_0.2.s390x as a component of Red Hat Enterprise Linux CodeReady Linux Builder EUS (v. 10.0)
- cjose-debugsource-0:0.6.2.2-7.el10_0.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
- cjose-debugsource-0:0.6.2.2-7.el10_0.2.x86_64 as a component of Red Hat Enterprise Linux CodeReady Linux Builder EUS (v. 10.0)
- cjose-devel-0:0.6.2.2-7.el10_0.2.aarch64 as a component of Red Hat Enterprise Linux CodeReady Linux Builder EUS (v. 10.0)
- cjose-devel-0:0.6.2.2-7.el10_0.2.ppc64le as a component of Red Hat Enterprise Linux CodeReady Linux Builder EUS (v. 10.0)
- cjose-devel-0:0.6.2.2-7.el10_0.2.s390x as a component of Red Hat Enterprise Linux CodeReady Linux Builder EUS (v. 10.0)
- cjose-devel-0:0.6.2.2-7.el10_0.2.x86_64 as a component of Red Hat Enterprise Linux CodeReady Linux Builder EUS (v. 10.0)
✅ Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Workaround: Until the fixed package is installed, applications using cjose for JWE encryption can avoid the vulnerable code path by switching the content-encryption algorithm from AES-CBC-HMAC (A128CBC-HS256, A192CBC-HS384, A256CBC-HS512) to an AES-GCM enc (A128GCM, A192GCM, or A256GCM), by using alg=dir with a caller-supplied content-encryption key, or by not using cjose for JWE encryption with the affected algorithm pair. These options protect newly created ciphertexts only; data already encrypted under the all-zero key must be considered compromised, should be re-encrypted, and any secrets it contained should be rotated. Upgrading to a version containing the upstream fix (0.6.2.6 or later) resolves the issue.