Unrated

libcurl incomplete mTLS config matching in connection 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 prior one. In affected versions, the configuration comparison was incomplete for some mTLS-related options: certain client-certificate-associated TLS settings, particularly private-key-related options, were omitted from the reuse eligibility checks. As a result, libcurl could incorrectly reuse a previously established connection even after the application changed client certificate or private key settings that should have forced creation of a new connection. The issue affects libcurl versions 7.7 through 8.20.0, was first introduced in curl 7.7 on 2001-03-22, does not affect the curl command-line tool, and is noted as similar to CVE-2022-27782.

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. A request intended to be performed under one client-certificate/private-key identity may instead be sent over an already-established connection authenticated with a different client identity. This can cause incorrect client authentication at the peer, misbinding of requests to the wrong certificate context, and unintended access or action under the previously authenticated identity. The available content does not indicate confirmed in-the-wild exploitation.

Mitigation

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

Avoid connection/handle reuse across transfers when changing mTLS client-authentication settings, especially client certificate and private key options. Operationally, isolate transfers that use different client identities so they cannot share pooled connections. Where feasible, disable or constrain connection reuse for workflows that rotate or switch client certificates until patched versions are deployed.

Remediation

Patch, then assume compromise.

Upgrade to curl/libcurl 8.21.0 or later, which contains the fix for CVE-2026-8932. If immediate upgrade is not possible, apply the upstream patch referenced by the curl advisory and rebuild affected software. Verify that all products embedding libcurl are updated, since the issue affects libcurl integrations rather than the curl CLI.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

ACTIVITY FEED

Recent activity

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

14 SOURCESView more in app

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.

security weekNews

Jun 25, 2026

25-Year-Old Vulnerability Patched in Curl - SecurityWeek

An authentication bypass vulnerability in libcurl caused by improper reuse of existing connections after client certificate or private key settings changed.

+3 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