CVE-2026-63073 OpenSSL CVE debrief

Who should care

Defenders responsible for OpenSSL CMP clients, particularly those using versions 3.4.0-3.4.7, 3.5.0-3.5.8, 3.6.0-3.6.4, and 4.0.0-4.0.2, should assess exposure and prioritize patching or compensating controls.

Why it matters

The OpenSSL CMP response validation vulnerability allows a malicious or intercepted CMP endpoint to crash a CMP client, resulting in a denial of service. Defenders should prioritize verifying exposure and applying patches or compensating controls.

• Denial of service (DoS) via crashing of CMP clients
• Verification of exposure for CMP clients using vulnerable OpenSSL versions
• Prioritization of patching or compensating controls for vulnerable systems
• Monitoring for unusual CMP response activity

Technical summary

The OpenSSL CMP response validation vulnerability occurs when validating a received CMP message. The peer-supplied sender distinguished name is converted with X509_NAME_oneline() and passed directly as the format argument to ERR_raise_data(). This allows an attacker to control the format string, causing a denial of service when the response comes from a malicious or intercepted CMP endpoint. The issue is limited to CMP clients that configure an expected sender or pin a server certificate. The vulnerability affects OpenSSL versions 3.4.0-3.4.7, 3.5.0-3.5.8, 3.6.0-3.6.4, and 4.0.0-4.0.2.

Defensive priority

Defenders should prioritize verifying exposure of CMP clients using OpenSSL versions 3.4.0-3.4.7, 3.5.0-3.5.8, 3.6.0-3.6.4, and 4.0.0-4.0.2, and applying patches or compensating controls.

Recommended defensive actions

• Verify OpenSSL versions 3.4.0-3.4.7, 3.5.0-3.5.8, 3.6.0-3.6.4, and 4.0.0-4.0.2 are updated to the latest patched versions.
• Review CMP client configurations for expected senders or pinned server certificates.
• Implement compensating controls, such as monitoring for unusual CMP response activity.
• 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.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.

Evidence notes

The vulnerability is caused by passing an attacker-controlled sender distinguished name as a format string to ERR_raise_data(). The issue is limited to CMP clients that configure an expected sender or pin a server certificate.

Sources and references

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.