JWE decryption and forgery via all-zero CEK
Published Sep 8, 2026 · Updated Sep 9, 2026
Cryptographic key generation in OpenIDC cjose 0.6.1 through 0.6.2.5 allows attackers to decrypt and forge affected JWEs. The _cjose_jwe_set_cek_aes_cbc() path in src/jwe.c inverts its random-allocation flag, zero-filling each fresh CEK instead of generating random bytes. Exposure requires AES-CBC-HMAC encryption with a key-management algorithm that asks the library to generate a CEK; anyone obtaining the JWE can read its plaintext and alter authenticated content.
Summary
What happened
Cryptographic key generation in OpenIDC cjose 0.6.1 through 0.6.2.5 allows attackers to decrypt and forge affected JWEs. The _cjose_jwe_set_cek_aes_cbc() path in src/jwe.c inverts its random-allocation flag, zero-filling each fresh CEK instead of generating random bytes. Exposure requires AES-CBC-HMAC encryption with a key-management algorithm that asks the library to generate a CEK; anyone obtaining the JWE can read its plaintext and alter authenticated content.
The record
- CVE
- CVE-2026-53939
- Published
- Sep 8, 2026
- Updated
- Sep 9, 2026
- Vendor
- OpenIDC
- Product
- cjose
- Classifications
- CWE-330, CWE-321, T1140
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 8, 2026CVE publishedPublication date reported by the CVE source.
- Sep 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 0.6.1, < 0.6.2.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Repeated encrypted_key proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo