Skip to main content
Mallory
UnratedVulnerability

CVE-2026-35328: Infinite loop in libtls supported_versions extension processing

Updated 2 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-35328CWE-835

CVE-2026-35328 is a vulnerability in libtls involving processing of the TLS supported_versions extension. According to the provided context, malformed or otherwise problematic handling of this extension can cause the affected code path to enter an infinite loop during TLS processing.

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.

Successful exploitation can cause the affected libtls-consuming process to hang indefinitely while processing a TLS handshake or related TLS input, resulting in denial of service for the targeted service or client process.

Mitigation

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

Until a vendor fix is available, reduce exposure by limiting access to services that accept untrusted TLS connections, placing vulnerable services behind filtering or rate-limiting controls, and monitoring for abnormal CPU utilization or hung processes associated with TLS session handling. If feasible, temporarily disable or isolate affected services that rely on vulnerable libtls builds when exposed to untrusted peers.

Remediation

Patch, then assume compromise.

The specific vendor remediation information is currently not available from the provided context. Remediation would require updating to a fixed libtls version once a vendor patch or security advisory is available.

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.
FAQ

Frequently asked questions

Is CVE-2026-35328 exploited in the wild?
As of Nov 19, 2026, Mallory has no reports of CVE-2026-35328 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-35328?
As of Nov 19, 2026, Mallory has found no public exploit for CVE-2026-35328.
Is there a patch for CVE-2026-35328?
The specific vendor remediation information is currently not available from the provided context. Remediation would require updating to a fixed libtls version once a vendor patch or security advisory is available.
Activity feed

Recent activity

5 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

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 activity4Community discussion across Reddit, Mastodon, and other social sources.