Finding and attribution
When TLS 1.3 certificate compression is compiled in, negotiated, and an available compression algorithm is used, the peer-supplied uncompressed certificate length can trigger large per-connection allocations (about 22 MiB) before decompression. OpenSSL says this can cause resource exhaustion but not memory corruption or disclosure.
Product: OpenSSL. AI system: AISLE autonomous analyzer (specific model/version not disclosed). Team / organization: AISLE.
CVE identifiers: CVE-2025-66199.
AI and human contribution (source account): AISLE’s January 26, 2026 article says its autonomous analyzer found all 12 CVEs in OpenSSL’s January coordinated release, and individually names this case. OpenSSL’s own vulnerability record credits the named Aisle Research finder(s) for CVE-2025-66199; OpenSSL’s January 27 security advisory gives the flaw and report chronology. The exact model and division of AI versus researcher analysis are not public. OpenSSL credits Tomas Dulka and Stanislav Fort (Aisle Research) as finders and fix developers; AISLE says its autonomous analyzer found all 12 cases. Exact human/AI division is not stated.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: OpenSSL published the vendor advisory and released fixes on January 27, 2026. The AISLE public AI attribution article appeared January 26, one day before the public vendor disclosure. No claim of in-the-wild exploitation is made.
Remediation status: fix documented. OpenSSL 3.6.1, 3.5.5, 3.4.4 and 3.3.6. See the OpenSSL advisory for affected release details; FIPS impact and exceptional configurations are stated in the advisory where applicable. This record does not establish deployment.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 27 Jan 2026. AI attribution dated 26 Jan 2026. Sources checked 15 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Medium · highest recorded score 5.9. Documented technical effects: denial of service.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
- CVE-2025-66199: CVSS 3.1 · 5.9 (Medium) ·
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H. CISA-ADP (ADP; CVE Program record) · checked 16 Nov 2026.
CVE-2025-66199: denial of service.
Prerequisites / affected scope: The CNA description states: 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..
Exploitation evidence: Exploitation in the wild is not established by the cited description.. Impact source · checked 16 Nov 2026.
Documented fix: OpenSSL 3.6.1, 3.5.5, 3.4.4 and 3.3.6. See the OpenSSL advisory for affected release details; FIPS impact and exceptional configurations are stated in the advisory where applicable. This record does not establish deployment.