{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2025-66199", "assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5", "state": "PUBLISHED", "assignerShortName": "openssl", "dateReserved": "2025-11-24T15:00:43.637Z", "datePublished": "2026-01-27T16:01:22.399Z", "dateUpdated": "2026-01-27T16:01:22.399Z"}, "containers": {"cna": {"affected": [{"defaultStatus": "unaffected", "product": "OpenSSL", "vendor": "OpenSSL", "versions": [{"lessThan": "3.6.1", "status": "affected", "version": "3.6.0", "versionType": "semver"}, {"lessThan": "3.5.5", "status": "affected", "version": "3.5.0", "versionType": "semver"}, {"lessThan": "3.4.4", "status": "affected", "version": "3.4.0", "versionType": "semver"}, {"lessThan": "3.3.6", "status": "affected", "version": "3.3.0", "versionType": "semver"}]}], "credits": [{"lang": "en", "type": "reporter", "value": "Tomas Dulka (Aisle Research)"}, {"lang": "en", "type": "reporter", "value": "Stanislav Fort (Aisle Research)"}, {"lang": "en", "type": "remediation developer", "value": "Tomas Dulka (Aisle Research)"}, {"lang": "en", "type": "remediation developer", "value": "Stanislav Fort (Aisle Research)"}], "datePublic": "2026-01-27T14:00:00.000Z", "descriptions": [{"lang": "en", "supportingMedia": [{"base64": false, "type": "text/html", "value": "Issue summary: A TLS 1.3 connection using certificate compression can be<br>forced to allocate a large buffer before decompression without checking<br>against the configured certificate size limit.<br><br>Impact summary: An attacker can cause per-connection memory allocations of<br>up to approximately 22 MiB and extra CPU work, potentially leading to<br>service degradation or resource exhaustion (Denial of Service).<br><br>In affected configurations, the peer-supplied uncompressed certificate<br>length from a CompressedCertificate message is used to grow a heap buffer<br>prior to decompression. This length is not bounded by the max_cert_list<br>setting, which otherwise constrains certificate message sizes. An attacker<br>can exploit this to cause large per-connection allocations followed by<br>handshake failure. No memory corruption or information disclosure occurs.<br><br>This issue only affects builds where TLS 1.3 certificate compression is<br>compiled in (i.e., not OPENSSL_NO_COMP_ALG) and at least one compression<br>algorithm (brotli, zlib, or zstd) is available, and where the compression<br>extension is negotiated. Both clients receiving a server CompressedCertificate<br>and servers in mutual TLS scenarios receiving a client CompressedCertificate<br>are affected. Servers that do not request client certificates are not<br>vulnerable to client-initiated attacks.<br><br>Users can mitigate this issue by setting SSL_OP_NO_RX_CERTIFICATE_COMPRESSION<br>to disable receiving compressed certificates.<br><br>The FIPS modules in 3.6, 3.5, 3.4 and 3.3 are not affected by this issue,<br>as the TLS implementation is outside the OpenSSL FIPS module boundary.<br><br>OpenSSL 3.6, 3.5, 3.4 and 3.3 are vulnerable to this issue.<br><br>OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue."}], "value": "Issue summary: A TLS 1.3 connection using certificate compression can be\nforced to allocate a large buffer before decompression without checking\nagainst the configured certificate size limit.\n\nImpact summary: An attacker can cause per-connection memory allocations of\nup to approximately 22 MiB and extra CPU work, potentially leading to\nservice degradation or resource exhaustion (Denial of Service).\n\nIn affected configurations, the peer-supplied uncompressed certificate\nlength from a CompressedCertificate message is used to grow a heap buffer\nprior to decompression. This length is not bounded by the max_cert_list\nsetting, which otherwise constrains certificate message sizes. An attacker\ncan exploit this to cause large per-connection allocations followed by\nhandshake failure. No memory corruption or information disclosure occurs.\n\nThis issue only affects builds where TLS 1.3 certificate compression is\ncompiled in (i.e., not OPENSSL_NO_COMP_ALG) and at least one compression\nalgorithm (brotli, zlib, or zstd) is available, and where the compression\nextension is negotiated. Both clients receiving a server CompressedCertificate\nand servers in mutual TLS scenarios receiving a client CompressedCertificate\nare affected. Servers that do not request client certificates are not\nvulnerable to client-initiated attacks.\n\nUsers can mitigate this issue by setting SSL_OP_NO_RX_CERTIFICATE_COMPRESSION\nto disable receiving compressed certificates.\n\nThe FIPS modules in 3.6, 3.5, 3.4 and 3.3 are not affected by this issue,\nas the TLS implementation is outside the OpenSSL FIPS module boundary.\n\nOpenSSL 3.6, 3.5, 3.4 and 3.3 are vulnerable to this issue.\n\nOpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue."}], "metrics": [{"format": "other", "other": {"content": {"text": "Low"}, "type": "https://openssl-library.org/policies/general/security-policy/"}}], "problemTypes": [{"descriptions": [{"cweId": "CWE-789", "description": "CWE-789 Memory Allocation with Excessive Size Value", "lang": "en", "type": "CWE"}]}], "providerMetadata": {"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5", "shortName": "openssl", "dateUpdated": "2026-01-27T16:01:22.399Z"}, "references": [{"name": "OpenSSL Advisory", "tags": ["vendor-advisory"], "url": "https://openssl-library.org/news/secadv/20260127.txt"}, {"name": "3.6.1 git commit", "tags": ["patch"], "url": "https://github.com/openssl/openssl/commit/6184a4fb08ee6d7bca570d931a4e8bef40b64451"}, {"name": "3.5.5 git commit", "tags": ["patch"], "url": "https://github.com/openssl/openssl/commit/895150b5e021d16b52fb32b97e1dd12f20448be5"}, {"name": "3.4.4 git commit", "tags": ["patch"], "url": "https://github.com/openssl/openssl/commit/966a2478046c311ed7dae50c457d0db4cafbf7e4"}, {"name": "3.3.6 git commit", "tags": ["patch"], "url": "https://github.com/openssl/openssl/commit/3ed1f75249932b155eef993a8e66a99cb98bfef4"}], "source": {"discovery": "UNKNOWN"}, "title": "TLS 1.3 CompressedCertificate excessive memory allocation", "x_generator": {"engine": "Vulnogram 0.2.0"}}}}

{}

{"cveTags": [], "descriptions": [{"lang": "en", "value": "Issue summary: A TLS 1.3 connection using certificate compression can be\nforced to allocate a large buffer before decompression without checking\nagainst the configured certificate size limit.\n\nImpact summary: An attacker can cause per-connection memory allocations of\nup to approximately 22 MiB and extra CPU work, potentially leading to\nservice degradation or resource exhaustion (Denial of Service).\n\nIn affected configurations, the peer-supplied uncompressed certificate\nlength from a CompressedCertificate message is used to grow a heap buffer\nprior to decompression. This length is not bounded by the max_cert_list\nsetting, which otherwise constrains certificate message sizes. An attacker\ncan exploit this to cause large per-connection allocations followed by\nhandshake failure. No memory corruption or information disclosure occurs.\n\nThis issue only affects builds where TLS 1.3 certificate compression is\ncompiled in (i.e., not OPENSSL_NO_COMP_ALG) and at least one compression\nalgorithm (brotli, zlib, or zstd) is available, and where the compression\nextension is negotiated. Both clients receiving a server CompressedCertificate\nand servers in mutual TLS scenarios receiving a client CompressedCertificate\nare affected. Servers that do not request client certificates are not\nvulnerable to client-initiated attacks.\n\nUsers can mitigate this issue by setting SSL_OP_NO_RX_CERTIFICATE_COMPRESSION\nto disable receiving compressed certificates.\n\nThe FIPS modules in 3.6, 3.5, 3.4 and 3.3 are not affected by this issue,\nas the TLS implementation is outside the OpenSSL FIPS module boundary.\n\nOpenSSL 3.6, 3.5, 3.4 and 3.3 are vulnerable to this issue.\n\nOpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue."}], "id": "CVE-2025-66199", "lastModified": "2026-01-27T16:16:15.777", "metrics": {}, "published": "2026-01-27T16:16:15.777", "references": [{"source": "openssl-security@openssl.org", "url": "https://github.com/openssl/openssl/commit/3ed1f75249932b155eef993a8e66a99cb98bfef4"}, {"source": "openssl-security@openssl.org", "url": "https://github.com/openssl/openssl/commit/6184a4fb08ee6d7bca570d931a4e8bef40b64451"}, {"source": "openssl-security@openssl.org", "url": "https://github.com/openssl/openssl/commit/895150b5e021d16b52fb32b97e1dd12f20448be5"}, {"source": "openssl-security@openssl.org", "url": "https://github.com/openssl/openssl/commit/966a2478046c311ed7dae50c457d0db4cafbf7e4"}, {"source": "openssl-security@openssl.org", "url": "https://openssl-library.org/news/secadv/20260127.txt"}], "sourceIdentifier": "openssl-security@openssl.org", "vulnStatus": "Received", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-789"}], "source": "openssl-security@openssl.org", "type": "Secondary"}]}

{}

{}