Skip to main content
Mallory
MediumVulnerability

CVE-2025-66199: OpenSSL TLS 1.3 Certificate Compression Excessive Memory Allocation

Published Jan 27, 2026 · Updated 12 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 1 in a dayToday
CVSS5.9Medium · v3.1
EPSS0.46%41st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
OpenSSL Software Foundation
IdentifiersCVE-2025-66199CWE-789 · Memory Allocation with Excessive…

CVE-2025-66199 is an excessive memory allocation vulnerability in OpenSSL TLS 1.3 certificate compression. During CompressedCertificate processing, the peer-supplied uncompressed certificate length is used to grow a heap buffer before decompression without checking it against max_cert_list, the configured certificate message size limit. A malicious peer can trigger allocations of up to approximately 22 MiB per connection and additional CPU work, followed by handshake failure, potentially causing denial of service. Both clients receiving compressed server certificates and servers requesting client certificates are affected when certificate compression is negotiated. Affected releases are OpenSSL 3.3 before 3.3.6, 3.4 before 3.4.4, 3.5 before 3.5.5, and 3.6 before 3.6.1. OpenSSL 3.0, 1.1.1, and 1.0.2 are unaffected. The flaw does not cause memory corruption or information disclosure.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

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

An unauthenticated remote peer can consume excessive heap memory and CPU resources during TLS handshakes. Each malicious connection can trigger allocations of up to approximately 22 MiB; repeated or concurrent attempts can degrade service or exhaust available resources, potentially denying service to legitimate users. Client applications are exposed through malicious TLS servers, while servers are exposed to client-initiated attacks only if they request client certificates. No confidentiality or integrity impact, memory corruption, or information disclosure is identified. OpenSSL FIPS modules are unaffected because TLS processing is outside their boundary; this does not exempt applications using those modules from the TLS vulnerability.

Mitigation

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

Set SSL_OP_NO_RX_CERTIFICATE_COMPRESSION to disable receiving compressed certificates. Alternatively, prevent negotiation of certificate compression or deploy a build without certificate compression support or available compression algorithms. The max_cert_list setting alone does not mitigate this flaw because the vulnerable allocation occurs without enforcing that limit.

Remediation

Patch, then assume compromise.

Upgrade OpenSSL to 3.6.1, 3.5.5, 3.4.4, or 3.3.6, or a later fixed release in the applicable branch. For distribution-managed or embedded OpenSSL, install the vendor update explicitly addressing CVE-2025-66199, since fixes may be backported without changing the upstream version number. Relevant fixed packages include Red Hat Enterprise Linux 9 OpenSSL 3.5.1-7.el9_7 and Red Hat Enterprise Linux 10 OpenSSL 3.5.1-7.el10_1. Product-specific fixes include HCL Compass 2.2.10.00.00_2026b, HCL VersionVault and DevOps Code ClearCase 11.0.1 or later, and PowerScale Node Firmware Package 13.2.5 or later for affected F210, F710, F910, and PA110 models.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
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
OpenSSL Software FoundationOpensslapplication
FAQ

Frequently asked questions

Is CVE-2025-66199 exploited in the wild?
As of Nov 6, 2026, Mallory has no reports of CVE-2025-66199 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-66199?
As of Nov 6, 2026, Mallory has found no public exploit for CVE-2025-66199.
Is there a patch for CVE-2025-66199?
Upgrade OpenSSL to 3.6.1, 3.5.5, 3.4.4, or 3.3.6, or a later fixed release in the applicable branch. For distribution-managed or embedded OpenSSL, install the vendor update explicitly addressing CVE-2025-66199, since fixes may be backported without changing the upstream version number.
What products are affected by CVE-2025-66199?
OpenSSL Software Foundation Openssl.
How severe is CVE-2025-66199?
CVE-2025-66199 has a CVSS v3.1 score of 5.9 (Medium) and an EPSS score of 0.46% (41st percentile) as of Nov 6, 2026.
Activity feed

Recent activity

39 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
tenable cloud security pluginsNews · Nov 5, 2026Echo: openssl-3.5.0: security update to 3.5.0+e1 | Tenable®A denial-of-service vulnerability in OpenSSL 3.3, 3.4, 3.5, and 3.6 allows a peer-supplied uncompressed certificate length to trigger heap allocations of approximately 22 MiB per connection and additional CPU work, bypassing the max_cert_list limit. It affects builds with TLS 1.3 certificate compression enabled, an available compression algorithm, and compression negotiated. Affected endpoints include clients receiving compressed server certificates and mutual-TLS servers receiving compressed client certificates. Servers that do not request client certificates are not vulnerable to client-initiated attacks. No memory corruption or information disclosure occurs. The listed CVSS v3 base score is 5.9.Read more ↗tenable otherNews · Jul 20, 2026[R1] Stand-alone Security Patch Available for Tenable Security Center Versions 6.6.0, 6.7.2 and 6.8.0: SC202607.1 - Security Advisory | Tenable®A vulnerability in OpenSSL addressed indirectly through upgraded third-party components in Tenable Security Center.Read more ↗the hacker newsNews · Jul 17, 2026OpenSSL HollowByte Flaw Could Freeze Server Memory with 11-Byte TLS RequestsA Low-severity OpenSSL TLS 1.3 certificate-compression memory-exhaustion bug where a peer-supplied length expands a heap buffer before validation.Read more ↗help net securityNews · Mar 2, 2026IPFire ships its 200th core update with a new domain blocklist and kernel upgrade - Help Net SecurityAn OpenSSL vulnerability patched by upgrading to OpenSSL 3.6.1 in IPFire Core Update 200.Read more ↗
+11 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

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, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity15Community discussion across Reddit, Mastodon, and other social sources.