incomplete mTLS config matching in conn reuse
libcurl contains a flaw in its connection reuse logic for mutual TLS (mTLS) sessions. When libcurl evaluates whether an existing pooled connection can be reused, some TLS configuration elements related to client-certificate authentication were not included in the configuration match checks. In particular, options related to the client private key could be omitted from the comparison, causing libcurl to incorrectly treat two different mTLS configurations as equivalent and reuse a previously established connection when it should have opened a new one. The issue affects libcurl versions 7.7 through 8.20.0, does not affect the curl command-line tool, and is noted by the vendor as similar to CVE-2022-27782.
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.
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.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Recent activity
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A low-severity curl/libcurl vulnerability involving incomplete mutual TLS configuration matching during connection reuse.
A low-severity libcurl vulnerability where incomplete matching of mTLS/client-certificate-related connection settings during connection reuse could allow reuse of a connection when changed client certificate or private key settings should have prevented it.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.