Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Medium

OpenSSL TLS 1.3 CompressedCertificate Excessive Memory Allocation DoS

IdentifiersCVE-2025-66199CWE-770

CVE-2025-66199 is a denial-of-service flaw in OpenSSL's handling of TLS 1.3 certificate compression. In affected OpenSSL 3.3, 3.4, 3.5, and 3.6 builds, when the certificate compression feature is compiled in and negotiated, the implementation uses the peer-supplied uncompressed certificate length from the TLS 1.3 CompressedCertificate message to grow a heap buffer before decompression. That length is not bounded by the configured max_cert_list certificate size limit, allowing a peer to force large allocations prior to handshake failure. The issue affects clients receiving a server CompressedCertificate and servers receiving a client CompressedCertificate in mutual TLS scenarios. The advisory states no memory corruption or information disclosure occurs.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A remote attacker can cause excessive per-connection memory allocation of up to approximately 22 MiB, along with additional CPU work for decompression handling, potentially degrading service or exhausting resources and causing denial of service. Exploitation results in handshake failure after resource consumption rather than code execution, memory corruption, or data disclosure.

Mitigation

If you can’t patch tonight, do this now.

Disable receiving TLS 1.3 compressed certificates by setting SSL_OP_NO_RX_CERTIFICATE_COMPRESSION. Additional risk reduction is possible by ensuring TLS 1.3 certificate compression is not compiled in or by avoiding availability/negotiation of certificate compression algorithms such as brotli, zlib, or zstd. Servers that do not request client certificates are not exposed to client-initiated exploitation in the server role.

Remediation

Patch, then assume compromise.

Upgrade OpenSSL to a fixed release: 3.6.1, 3.5.5, 3.4.4, or 3.3.6, as appropriate for the deployed branch. OpenSSL 3.0, 1.1.1, and 1.0.2 are not affected. Downstream products should be updated to vendor-provided releases that incorporate these fixes.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
FreebsdFreebsdapplication
OpenSSL Software FoundationOpensslapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity15

Community discussion across Reddit, Mastodon, and other social sources.