VulnTideExploited vulnerabilities, by vendor. Data as of .
Not in CISA KEVPublished CVSS 7.5 highEPSS 0.4% probability of exploitation in 30 daysFound by AI: AISLE
curl

CVE-2026-8932: incomplete mTLS config matching in conn reuse

Is it exploited?

Not on CISA's list. CISA has not added it to the Known Exploited Vulnerabilities catalog as of . If CISA adds it, this page shows it as known exploited.

How likely is exploitation in the next 30 days?
0.4%

EPSS score, percentile 33.8 of all scored records. A probability estimated by FIRST, not a report of exploitation.

CISA's SSVC assessment in the CVE record lists exploitation as poc.

How severe?
7.5 High

CVSS v3.1 base score, from CISA's enrichment of the record

What should I do?

CISA has set no required action, because the vulnerability is not in KEV.

The CVE record links no vendor advisory, patch or mitigation.

Which versions are affected?

Affected

  • from 7.7.0 to before 8.14.2
  • from 8.15.0 to before 8.16.1
  • from 8.17.0 to before 8.20.1
  • 8.20.0
  • 8.19.0
  • 8.18.0

and 9 more in the table below

Versions by product

Source: CISA KEV 2026.10.29, as of ; FIRST EPSS, as of ; CVE List, as of . About the data.

What to do

Advisories and patches

The CVE record links no vendor advisory, patch or mitigation.

This summary is based on the CVE record as of . Check the vendor's advisory before you act: affected versions and fixes can change.

Affected products and versions

As listed in the CVE record.

curl curl
StatusVersions
Affectedfrom 7.7.0 to before 8.14.2
Affectedfrom 8.15.0 to before 8.16.1
Affectedfrom 8.17.0 to before 8.20.1

Versions not listed are: unaffected.

curl curl
StatusVersions
Affectedfrom a1d6ad26100b to before 7541ae569d82

Versions not listed are: unaffected.

curl curl
StatusVersions
Affected8.20.0
Affected8.19.0
Affected8.18.0
Affected8.17.0
Affected8.16.0
Affected8.15.0
Affected8.14.1
Affected8.14.0
Affected8.13.0
Affected8.12.1
Affected8.12.0
Affected8.11.1

Versions not listed are: unaffected.

And 181 more version entries in the CVE record.

Source: CVE List, as of . About the data.

About this vulnerability

libcurl would reuse a previously created connection even when some mTLS config related option had been changed that should have prohibited reuse. libcurl keeps previously used connections in a connection pool for subsequent transfers to reuse if one of them matches the setup. However, some TLS settings related to client certificates were left out from the configuration match checks, making them…

Summary: CVE record, as of .

  • CISA has not added CVE-2026-8932 to its Known Exploited Vulnerabilities (KEV) catalog, as of 29 Oct 2026.
  • The CVE record was published on 3 Jul 2026.
  • The CVE record carries a CVSS v3.1 base score of 7.5 (High), taken from CISA's enrichment of the record.
  • FIRST's EPSS model puts the probability of exploitation in the next 30 days at 0.4% (percentile 33.8), as of 29 Oct 2026. EPSS is a statistical estimate, not a report of exploitation.
  • CISA's SSVC assessment in the CVE record: exploitation poc, automatable yes, technical impact partial.
  • The credits in the CVE record name AISLE as finder.

Source: CISA KEV 2026.10.29, as of ; CVE List, as of ; FIRST EPSS, as of . About the data.

Description

incomplete mTLS config matching in conn reuse

libcurl would reuse a previously created connection even when some mTLS config related option had been changed that should have prohibited reuse. libcurl keeps previously used connections in a connection pool for subsequent transfers to reuse if one of them matches the setup. However, some TLS settings related to client certificates were left out from the configuration match checks, making them match too easily. In particular options related to the private key.

Source: CVE List, as of . About the data.

Weakness

CWE-305

CWE and CAPEC are maintained by MITRE; the entries are those named in the CVE record.

Timeline

DateEvent
CVE record published
CVE record last updated

References

3