PatchSiren cyber security CVE debrief
CVE-2026-63074 OpenSSL CVE debrief
The OpenSSL Certificate Management Protocol (CMP) vulnerability allows for potential Denial of Service (DoS) attacks and Out-of-Memory (OOM) conditions due to unbounded cache growth. Defenders responsible for OpenSSL CMP servers, security teams managing OpenSSL deployments, and administrators of systems using affected OpenSSL versions should assess exposure and prioritize patching. The vulnerability was published on 2026-08-25T13:19:26.283Z and has not been modified since then. The NVD entry is currently Analyzed. A malicious client may flood a CMP server with requests driving unbounded growth of the cache of extraCerts, potentially leading to OOM conditions.
- Vendor
- OpenSSL
- Product
- Unknown
- CVSS
- MEDIUM 5.9
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-25
- Original CVE updated
- 2026-09-11
- Advisory published
- 2026-08-25
- Advisory updated
- 2026-09-11
Who should care
Defenders responsible for OpenSSL CMP servers, security teams managing OpenSSL deployments, and administrators of systems using affected OpenSSL versions should assess exposure and prioritize patching.
Why it matters
The OpenSSL CMP cache unbounded growth vulnerability allows for potential DoS attacks and OOM conditions, requiring defenders to assess exposure, prioritize patching, and monitor for unusual activity.
- Potential for OOM conditions due to unbounded cache growth
- Denial of Service (DoS) attacks through repeated sending of rejected CMP messages with large lists of additional certificates
- Need for verification of OpenSSL version and exposure in environments
- Priority for patching and updating affected OpenSSL versions
Technical summary
The OpenSSL Certificate Management Protocol (CMP) caches additional certificates sent in a CMP message but never expunges them if they are invalid. A malicious client may flood a CMP server with requests driving unbounded growth of the cache of extraCerts, potentially leading to OOM conditions. This issue was fixed by removing the added extra certs if the message is rejected, using the same method as when the context is configured to not do caching at all. The vulnerability affects OpenSSL versions 3.0.0 to 3.0.22, 3.4.0 to 3.4.7, 3.5.0 to 3.5.8, 3.6.0 to 3.6.4, and 4.0.0 to 4.0.2.
Defensive priority
Defenders should prioritize verifying and applying patches for OpenSSL versions 3.0.0 to 3.0.22, 3.4.0 to 3.4.7, 3.5.0 to 3.5.8, 3.6.0 to 3.6.4, and 4.0.0 to 4.0.2, and assess exposure in their environments.
Recommended defensive actions
- Verify and apply patches for OpenSSL versions 3.0.0 to 3.0.22, 3.4.0 to 3.4.7, 3.5.0 to 3.5.8, 3.6.0 to 3.6.4, and 4.0.0 to 4.0.2
- Assess exposure in environments using OpenSSL CMP servers
- Monitor for unusual CMP activity and cache growth
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The OpenSSL Certificate Management Protocol (CMP) caches additional certificates sent in a CMP message but never expunges them if they are invalid. A malicious client may flood a CMP server with requests driving unbounded growth of the cache of extraCerts, potentially leading to OOM conditions.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-63074 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-63074
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-63074 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-63074
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/openssl/openssl/commit/01e567978a55fba18142a230380c31296049fae7
[email protected] - Patch
-
Source reference
Unverified legacy reference
URL: https://github.com/openssl/openssl/commit/21a5d9658b0c66daace60e10ea18ff32a448de9f
[email protected] - Patch
-
Source reference
Unverified legacy reference
URL: https://github.com/openssl/openssl/commit/74ae7f6df47a5767c1010b88c47507dfc5b32c46
[email protected] - Patch
-
Source reference
Unverified legacy reference
URL: https://github.com/openssl/openssl/commit/75360af9650d4e0c82ba0050c5c9912cd79e54af
[email protected] - Patch
-
Source reference
Unverified legacy reference
URL: https://github.com/openssl/openssl/commit/f636f9ca0fa1bae5b42f9e787f025c96fb09c43a
[email protected] - Patch
-
Source reference
Unverified legacy reference
URL: https://openssl-library.org/news/secadv/20260825.txt
[email protected] - Vendor Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.