LiveActive security incident?Get immediate response
CVE Record

CVE-2026-63073: Untrusted Sender DN Used as Format String in CMP Response Validation

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.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A malicious or intercepted certificate-management server can send a crafted response that crashes an affected OpenSSL CMP client. Exposure requires CMP use with an expected sender or pinned server certificate. The supplied evidence supports denial of service, not reliable data theft, tampering, or remote code execution.

Executive priority

Treat as urgent where CMP supports certificate enrollment or renewal, because repeated crashes could disrupt certificate operations without credentials or user interaction. Prioritize confirmed vulnerable CMP clients; broader OpenSSL deployments without CMP exposure do not warrant the same urgency.

Technical view

OpenSSL passes a peer-controlled sender distinguished name directly to ERR_raise_data() as a format string. Surviving percent specifiers can cause invalid reads or writes through unrelated stack values. The vulnerable validation path applies when CMP clients configure an expected sender or derive one from a pinned server certificate.

Likely exposure

Likely exposure is limited to CMP clients using OpenSSL 4.0.0, 3.6.0, 3.5.0, or 3.4.0 with expected-sender validation or a pinned server certificate. Systems not using CMP, including OpenSSL FIPS modules, are not identified as affected.

Exploitation context

No active exploitation is established: the source bundle states this CVE is not in KEV. Exploitation requires a malicious CMP endpoint or interception of CMP traffic, plus the relevant sender-validation configuration. The reliable outcome described is client denial of service; controlled memory access and remote code execution are unsupported.

Researcher notes

The supplied CVSS 9.8 vector claims high confidentiality, integrity, and availability impact, but the technical narrative explicitly limits the reliable consequence to denial of service. Researchers should preserve that distinction. The format string is attacker-controlled, but variadic arguments are not, preventing a supported claim of controlled writes, reads, or code execution.

Mitigation direction

  • Apply the corresponding fixed release or patch: 4.0.2, 3.6.4, 3.5.8, or 3.4.7.
  • Prioritize internet-facing or operationally critical systems that initiate CMP transactions.
  • Review vendor guidance before applying temporary configuration changes or compensating controls.
  • Restrict CMP connectivity to trusted endpoints and monitor for unexpected endpoint or certificate changes.

Validation and detection

  • Inventory OpenSSL versions on systems and applications that initiate CMP requests.
  • Confirm whether CMP clients configure an expected sender or pin a server certificate.
  • Verify deployed builds contain the applicable referenced OpenSSL patch commit.
  • Review CMP client crashes and error logs around response sender validation.
  • Confirm OpenSSL FIPS module usage is not mistakenly treated as exposure by itself.
Prepared
Confidence
high
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-134: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-63073 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-63073Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
OpenSSLOpenSSL4.0.0, 3.6.0, 3.5.0, 3.4.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-134 · source CWE mapping

Use of Externally-Controlled Format String

Use of Externally-Controlled Format String represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.