Unrated

incomplete mTLS config matching in conn reuse

IdentifiersCVE-2026-8932CWE-305

CVE-2026-8932 is a low-severity authentication bypass flaw in libcurl’s connection reuse logic for mutual TLS (mTLS). libcurl maintains a connection pool and may reuse an existing TLS connection when it determines that the new transfer’s configuration matches the existing connection. In affected versions, the configuration matching was incomplete for some mTLS-related options: certain client-certificate settings, particularly private-key-related options, were not included in the reuse eligibility checks. As a result, libcurl could incorrectly reuse a previously established connection even after the application changed the client certificate or private key settings, in cases where a new connection should have been required. This issue affects libcurl versions 7.7 through 8.20.0 and does not affect the curl command-line tool.

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.

Start free trial

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.

Successful exploitation can cause authentication bypass in libcurl-based applications using mTLS. An application that expects a new TLS connection to be established with updated client certificate or private key material may instead continue using an already authenticated connection created under prior credentials. This can result in requests being sent over a connection authenticated with the wrong client identity, undermining certificate-based access controls and potentially causing authorization confusion between tenants, users, or security contexts that rely on distinct client certificates.

Mitigation

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

If patching cannot be performed immediately, avoid connection reuse when changing client certificate details or private key settings between requests. Operationally, applications should ensure that transfers using different mTLS identities do not share reusable libcurl connection state or pools. Segregating handles, disabling reuse for such workflows, or forcing fresh connections when client-authentication parameters change can reduce exposure until the fixed version is deployed.

Remediation

Patch, then assume compromise.

Upgrade curl/libcurl to version 8.21.0 or later, which contains the fix for CVE-2026-8932. If immediate upgrade is not possible, apply the vendor patch referenced in the curl advisory and rebuild affected software against the patched libcurl. Confirm that all deployed applications embedding or dynamically linking libcurl are updated, as the issue affects libcurl consumers rather than the curl command-line tool.

PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.

VALID 0 / 1 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

ACTIVITY FEED

Recent activity

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

15 SOURCESView more in app

scworldNews

Jun 26, 2026

Curl fixes 18 vulnerabilities, including a 25-year-old bug | brief | SC Media

An authentication bypass vulnerability in libcurl where an existing connection may be reused after client certificate or private key settings change.

security affairsNews

Jun 25, 2026

Tata Electronics Confirms Data Breach After 630GB Leak Claim Targets Apple and Tesla

CVE-2026-8932 is only mentioned as a tag/reference in the article metadata and no vulnerability details are provided in the content.

security affairsNews

Jun 25, 2026

Curl Fixes a 25-Year-Old Bug in Its Largest CVE Release Yet - Security Affairs

An authentication bypass vulnerability in libcurl's mTLS connection reuse logic where an existing connection could be reused even after client certificate or private key settings changed. The issue reportedly dates back to curl 7.7 in March 2001.

cyber security newsNews

Jun 25, 2026

25-Year-Old Vulnerability in curl Used by 30 Billion Devices Finally Patched

An authentication bypass vulnerability in curl/libcurl caused by incomplete mTLS configuration matching during connection reuse. It is significant because it existed for over 25 years and could allow reuse of a connection after client certificate changes.

+4 more in the timeline

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.

Start free trial

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 activity7

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

EXTERNAL REFERENCES

MITRE CVE

cve.org · CVE-2026-8932

NVD

nvd.nist.gov/vuln/detail/CVE-2026-8932

MITRE CWE · CWE-305

cwe.mitre.org