Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
9.8

Docker OpenSSL images allow CMP client crash

published 1 day ago
Summary

The OpenSSL library used in Docker hardened images can crash a client that checks CMP server responses when the server sends a specially crafted name containing percent signs. The problem occurs only when the client is set to expect a particular sender or uses a pinned certificate. Upgrade to a version of the OpenSSL package that fixes the format‑string handling, or disable strict sender checking until the update is applied.

What to do

The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.

Affected software
Ecosystem VendorProductAffected versions
Docker Hardened Images:Alpine:3.23 docker hardened images openssl-provider-fips All versions
Docker Hardened Images:Alpine:3.24 docker hardened images openssl-provider-fips All versions
Docker Hardened Images:Alpine:3.23 docker hardened images openssl All versions
Docker Hardened Images:Alpine:3.24 docker hardened images openssl All versions
Docker Hardened Images:Debian:13 docker hardened images openssl All versions
Original advisory text
Issue summary: OpenSSL CMP response validation passed an unexpected response
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.
References
Fix within
Internet-facing 3 days
Internal 60 days
  • Not known to be exploited
  • Can be exploited automatically (estimated)
  • Gives an attacker full control (estimated)
Severity
9.8 Critical
Timeline
Published20 Nov 2026
Updated20 Nov 2026
First seen20 Nov 2026
Sources
Track software like this
Free during beta