CVE-2026-53939

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 90% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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).

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
72(Attend)
EG Risk 72/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

September 8, 2026

Last Modified

September 10, 2026

Advisory Details (3)

Auto-updated Sep 15, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available

all-zero Content Encryption Key used for AES-CBC-HMAC JWE encryption · Advisory · OpenIDC/cjose · GitHub

https://github.com/OpenIDC/cjose/security/advisories/GHSA-f6wf-pqg3-6wqq
github_release Patch Available

release 0.6.2.6

Patch available: OpenIDC/cjose v0.6.2.6

https://github.com/OpenIDC/cjose/releases/tag/v0.6.2.6
github_commit

commit 2a6e5bd969fa (OpenIDC/cjose)

Fix landed in OpenIDC/cjose commit 2a6e5bd969fa — awaiting tagged release

https://github.com/OpenIDC/cjose/commit/2a6e5bd969fa20059fb00913fb9f57d77ea6a4d9

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 18:04 UTCEG score recompute
  2. 2026-09-18 21:21 UTCEG score recompute
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-17 20:16 UTCEG score recompute
  5. 2026-09-17 19:31 UTCEPSS rescore
  6. 2026-09-16 18:15 UTCEG score recompute
  7. 2026-09-16 14:08 UTCEPSS rescore
  8. 2026-09-16 05:43 UTCEG score recompute
  9. 2026-09-16 05:15 UTCEPSS rescore
  10. 2026-09-15 05:22 UTCEG score recompute
  11. 2026-09-13 16:52 UTCEG score recompute
  12. 2026-09-13 16:47 UTCEPSS rescore
  13. 2026-09-12 16:35 UTCEG score recompute
  14. 2026-09-11 16:17 UTCEG score recompute
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-11 12:14 UTCEG score recompute
  17. 2026-09-10 11:14 UTCEG score recompute
  18. 2026-09-10 09:35 UTCEPSS rescore
  19. 2026-09-09 16:46 UTCEG score recompute
  20. 2026-09-09 15:30 UTCEG score recompute
  21. 2026-09-09 00:35 UTCEG score recompute
  22. 2026-09-08 23:41 UTCEG score recompute
  23. 2026-09-08 23:38 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-53939?
CVE-2026-53939 is a critical vulnerability published on September 8, 2026. 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…
When was CVE-2026-53939 disclosed?
CVE-2026-53939 was first published in the National Vulnerability Database on September 8, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53939 actively exploited?
CVE-2026-53939 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 90.3% of all scored CVEs.
What is the CVSS score of CVE-2026-53939?
CVE-2026-53939 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-53939?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53939, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53939

Explore →

Is Your Infrastructure Affected by CVE-2026-53939?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.