CVE-2026-35328: Infinite loop in libtls supported_versions extension processing
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.
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.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
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.
Recent activity
5 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.