CVE-2025-66199
Medium · 5.9CVSS
5.9
EPSS
0.5%
Published
Jan 27, 2026
CISA due date
—
The record
Issue summary: A TLS 1.3 connection using certificate compression can be forced to allocate a large buffer before decompression without checking against the configured certificate size limit. Impact summary: An attacker can cause per-connection memory allocations of up to approximately 22 MiB and extra CPU work, potentially leading to service degradation or resource exhaustion (Denial of Service). In affected configurations, the peer-supplied uncompressed certificate length from a CompressedCertificate message is used to grow a heap buffer prior to decompression. This length is not bounded by the max_cert_list setting, which otherwise constrains certificate message sizes. An attacker can exploit this to cause large per-connection allocations followed by handshake failure. No memory corruption or information disclosure occurs. This issue only affects builds where TLS 1.3 certificate compression is compiled in (i.e., not OPENSSL_NO_COMP_ALG) and at least one compression algorithm (brotli, zlib, or zstd) is available, and where the compression extension is negotiated. Both clients receiving a server CompressedCertificate and servers in mutual TLS scenarios receiving a client CompressedCertificate are affected. Servers that do not request client certificates are not vulnerable to client-initiated attacks. Users can mitigate this issue by setting SSL_OP_NO_RX_CERTIFICATE_COMPRESSION to disable receiving compressed certificates. The FIPS modules in 3.6, 3.5, 3.4 and 3.3 are not affected by this issue, as the TLS implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4 and 3.3 are vulnerable to this issue. OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| AlmaLinux:10 | openssl | 0 | 1:3.5.1-7.el10_1.alma.1 |
| AlmaLinux:10 | openssl-devel | 0 | 1:3.5.1-7.el10_1.alma.1 |
| AlmaLinux:10 | openssl-libs | 0 | 1:3.5.1-7.el10_1.alma.1 |
| AlmaLinux:10 | openssl-perl | 0 | 1:3.5.1-7.el10_1.alma.1 |
| Chainguard | libcrypto3-2.34 | 0 | 3.6.1-r0 |
| Chainguard | openssl | 0 | 3.6.1-r0 |
| Chainguard | openssl-provider-fips-3.4.0 | 0 | 0 |
| Chainguard | openssl-provider-fips-3.4.0 | 0 | 3.4.0-r4 |
| Chainguard | openssl-provider-fips-3.6.0 | 0 | 0 |
| Chainguard | openssl-provider-fips-3.6.0 | 0 | 3.6.0-r2 |
| Wolfi | openssl | 0 | 3.6.1-r0 |
| openSUSE:Leap 16.0 | openssl-3 | 0 | 3.5.0-160000.5.1 |
| openSUSE:Tumbleweed | openssl-3 | 0 | 3.5.3-2.1 |
Related vulnerabilities
- CVE-2026-22795 Issue summary: An invalid or NULL pointer dereference can happen in an application… Also affects openssl
- CVE-2026-22796 Issue summary: A type confusion vulnerability exists in the signature verification of… Also affects openssl
- CVE-2025-69419 Issue summary: Calling PKCS12_get_friendlyname() function on a maliciously crafted… Also affects openssl
- CVE-2025-69420 Issue summary: A type confusion vulnerability exists in the TimeStamp Response… Also affects openssl
- CVE-2025-69421 Issue summary: Processing a malformed PKCS#12 file can trigger a NULL pointer dereference… Also affects openssl
- CVE-2025-69418 Issue summary: When using the low-level OCB API directly with AES-NI orother… Also affects openssl
- CVE-2025-68160 Issue summary: Writing large, newline-free data into a BIO chain using the line-buffering… Also affects openssl
- CVE-2025-11187 Issue summary: PBMAC1 parameters in PKCS#12 files are missing validation which can… Also affects openssl