CVE-2026-63073
UNSCOREDDescription
Issue summary: OpenSSL CMP response validation passed an unexpected response sender distinguished name directly as the format string to `ERR_raise_data()`. Impact summary: A malicious or intercepted CMP endpoint can crash a CMP client that enforces an expected sender or uses a pinned server certificate whose subject becomes the default expected sender. CWE: CWE-134 (Use of Externally-Controlled Format String) Description: When validating a received CMP message, ossl_cmp_msg_check_update() converts the peer-supplied sender distinguished name with X509_NAME_oneline() and passes it directly as the format argument to ERR_raise_data(). Percent characters survive the conversion, so a sender DN such as "CN=%s%n" reaches BIO_vsnprintf() as an attacker-controlled format string with no matching variadic arguments. This path is only reached when the caller configures an expected sender or pins a server certificate, which is the normal configuration for a CMP client validating server responses. Since the attacker controls the format string but none of the variadic arguments, such specifiers as %s and %n dereference or write through unrelated stack contents and crash the client. The reliable consequence is a denial of service, when the response comes from a malicious or intercepted CMP endpoint. There is no controlled memory write, arbitrary-address read, or reliable path to remote code execution. FIPS impact: no No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3.1 Vector
No CVSS vector data available.
Exploit Intelligence
Low risk: more likely to be exploited than 34% of all known CVEs.
References
Related Vulnerabilities
Other CWE-134 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2020-13160 | Critical | 9.8 | 81% | - | Fix |
| CVE-2023-22374 | High | 8.5 | 73% | - | - |
| CVE-2012-1851 | High | 10.0 | 66% | - | - |
| CVE-2024-23113 | Critical | 9.8 | 62% | KEV | - |
| CVE-2012-3569 | High | 9.3 | 48% | - | - |
| CVE-2019-1579 | High | 8.1 | 46% | KEV + Ransom | Fix |
Common questions
How do I fix CVE-2026-63073?
Published advisories record a fix for 8 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2026-63073 being actively exploited?
Not that we know of. CVE-2026-63073 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.41% is the estimated probability that it will be exploited in the next 30 days. That is higher than 34% of all scored CVEs.
What does CVE-2026-63073 affect?
Published advisories record a fix for openssl (Debian), openssl (Rocky), openssl (Red Hat / RHEL), openssl3 (Red Hat / RHEL), and 4 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-63073
Markdown
[](https://tridentstack.com/cve/CVE-2026-63073)HTML
<a href="https://tridentstack.com/cve/CVE-2026-63073"><img src="https://tridentstack.com/cve/badge/CVE-2026-63073.svg" alt="CVE-2026-63073"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-28.