CVE-2026-63073: OpenSSL CMP Response Validation Format-String Denial of Service
- Vendor
- OpenSSL Software Foundation
CVE-2026-63073 is an externally controlled format-string vulnerability in OpenSSL Certificate Management Protocol (CMP) response validation. When processing an unexpected sender distinguished name, ossl_cmp_msg_check_update() converts the peer-supplied name using X509_NAME_oneline() and passes the result directly as the format argument to ERR_raise_data(). Percent characters survive conversion, allowing attacker-controlled format specifiers to reach BIO_vsnprintf() without matching variadic arguments. The vulnerable path requires an expected sender to be configured explicitly or derived from a pinned server certificate. A malicious or intercepted CMP endpoint can trigger invalid memory accesses and crash the client. OpenSSL FIPS modules are unaffected because CMP processing is outside the FIPS module boundary.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation causes denial of service by crashing the CMP client process, potentially interrupting certificate-management operations and other functionality hosted in the same process. Format specifiers can dereference or write through unrelated stack contents, but the vulnerability does not provide a controlled memory write, arbitrary-address read, or reliable remote-code-execution path. Confidentiality or integrity compromise is not established.
Mitigation
If you can’t patch tonight, do this now.
Until patched, restrict CMP client connections to trusted servers over authenticated, integrity-protected transport and use network controls to reduce interception and exposure to untrusted endpoints. These restrictions do not protect against a malicious trusted endpoint. Monitor unexpected CMP client crashes. Do not disable expected-sender validation or certificate pinning as a workaround.
Remediation
Patch, then assume compromise.
Install the vendor-provided OpenSSL security update applicable to the deployed release and packaging. Identified fixed packages include OpenSSL 3.5.8 for the upstream 3.5 branch, Echo 3.5.0+e1 or later, Debian trixie 3.5.7-1~deb13u2 or later, Ubuntu 26.04 LTS 3.5.5-1ubuntu3.4, RHEL 9 3.5.8-1.el9_8, and RHEL 10 3.5.8-1.el10_2. For applications and containers bundling OpenSSL, install the corresponding vendor-fixed product release or rebuild with a corrected library. Restart or redeploy dependent processes after updating so they load the patched library.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-63073 exploited in the wild?
- As of Nov 7, 2026, Mallory has no reports of CVE-2026-63073 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-63073?
- As of Nov 7, 2026, Mallory has found no public exploit for CVE-2026-63073.
- Is there a patch for CVE-2026-63073?
- Install the vendor-provided OpenSSL security update applicable to the deployed release and packaging. Identified fixed packages include OpenSSL 3.5.8 for the upstream 3.5 branch, Echo 3.5.0+e1 or later, Debian trixie 3.5.7-1~deb13u2 or later, Ubuntu 26.04 LTS 3.5.5-1ubuntu3.4, RHEL 9 3.5.8-1.el9_8, and RHEL 10 3.5.8-1.el10_2.
- What products are affected by CVE-2026-63073?
- OpenSSL Software Foundation Openssl.
- How severe is CVE-2026-63073?
- CVE-2026-63073 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 1.2% (68th percentile) as of Nov 7, 2026.
Recent activity
45 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.