Quick answers
- Is CVE-2026-63074 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63074 being exploited in the wild.
- How severe is CVE-2026-63074?
- Medium severity, with a CVSS score of 5.9, published 25 August 2026.
- Which products and versions are affected?
- OpenSSL OpenSSL.
- Is there a fix for CVE-2026-63074?
- A patch was published on 2026-08-24: Patches merged as commits 01e5679 and 21a5d96 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-63074 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-63074?
- Check whether you run OpenSSL. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a resource exhaustion flaw (CWE-770) in OpenSSL's CMP implementation where the extraCerts cache in a reused OSSL_CMP_CTX context is never expunged after a message rejection. When a CMP server reuses a single context object across multiple requests, an attacker can send malformed CMP messages with large lists of extraCerts; even though the message is rejected, the certificates remain in the server's untrusted certificate stack. An attacker with network access to a CMP server can exploit this without authentication by repeatedly sending CMP messages with unique extra certificates, causing unbounded memory growth. The fix, applied in commits 01e5679 and 21a5d96, removes cached extra certificates when a message is rejected, treating rejected messages the same as when caching is disabled.
Affected products
- OpenSSL OpenSSL
Timeline
- 2026-08-25: disclosed
- 2026-08-24: patched: Patches merged as commits 01e5679 and 21a5d96