5.9

CVE-2025-66199: TLS 1.3 CompressedCertificate excessive memory allocation

Analyzed
AliasesALPINE-CVE-2025-66199UBUNTU-CVE-2025-66199DEBIAN-CVE-2025-66199
Published 27-01-2026Last modified 29-01-2026

Vulnerability summary

CVE-2025-66199 is a medium (CVSS 5.9) vulnerability in openssl. EPSS estimates a 0.46% chance of exploitation in the next 30 days, higher than 40.1% of scored vulnerabilities.

Priority
Routine

Not severe (CVSS 5.9, network access); no exploitation reported by the 5 checked sources

Source freshness unavailable

How is this decided?
CVSS score
5.9/10
010
Medium · v3.1 (CVE.org)
EPSS score
0.46%
0%100%
Low · +0.01 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 8 · Related 6

Timeline

  1. 27-01-2026
    PublishedVulnerability first disclosed.
  2. 29-01-2026
    Last modifiedVulnerability information updated.

Description

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.

CVSS metrics

7 scores · 7 sources · 1 version

EPSS trend

Probability

0.46%

Chance of exploitation in the next 30 days

Percentile

40%

Versus all other CVEs

30-day change

Increase +0.01 pp

From 0.45% on 04-10-2026

04-10-202603-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Version check

Known conditions: network-reachable, no authentication, no user interaction (CVSS vector). Other conditions: not stated in public data.

Chainguard8 products
  • libcrypto3-2.34< 3.6.1-r0
  • openssl< 3.6.1-r0
  • openssl-3.5< 3.5.5-r0
  • openssl-3.5-libcrypto< 3.5.5-r0
  • openssl-3.5-libssl< 3.5.5-r0
Ubuntu4 products
  • edk2All versions (No fix recorded)
  • edk2-hweAll versions (No fix recorded)
  • nodejsAll versions (No fix recorded)
  • openssl< 3.5.3-1ubuntu3 | < 3.5.5-1ubuntu1
Alpine1 product
  • openssl≥ 3.3.0, < 3.3.6-r0 | ≥ 3.3.0, < 3.5.5-r0
Debian1 product
  • openssl< 3.5.4-1~deb13u2 | < 3.5.5-1
Openssl1 product
  • openssl≥ 3.3.0, < 3.3.6 | ≥ 3.4.0, < 3.4.4 | ≥ 3.5.0, < 3.5.5 | ≥ 3.6.0, < 3.6.1
Wolfi1 product
  • openssl< 3.6.1-r0

6 vendors · 16 products

References

12 links
Show all 12 references