Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-8932

incomplete mTLS config matching in conn reuse

Description

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.

Public exploit

An exploit or proof of concept is public: anyone can try it against an unpatched system. A reference of the record is tagged as an exploit. CISA's SSVC rates its exploitation: a proof of concept is public.

Show the exploits1

References tagged exploit1 reference

Timeline

  1. ID reserved

    By curl

  2. · 45 days later

    Published

  3. · 2 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-8932, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVDNVD · Modified3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS (exploitation in 30 days)
0.40% · top 66% of all CVEs (12 Nov 2026)
CISA SSVC
Exploitation: poc · Automatable: yes · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.

Affected products

  • curl · curl

    • affected 7.7.0 – < 8.14.2
    • affected 8.15.0 – < 8.16.1
    • affected 8.17.0 – < 8.20.1

  • curl · curl

    • affected a1d6ad26100bc493c7b04f1301b1634b7f5aa8b4 – < 7541ae569d82fb308a5e2d94916027da4fa3ba3e

  • curl · curl

    • affected 8.20.0
    • affected 8.19.0
    • affected 8.18.0
    • affected 8.17.0
    • affected 8.16.0
    • affected 8.15.0
    • affected 8.14.1
    • affected 8.14.0
    • affected 8.13.0
    • affected 8.12.1
    • affected 8.12.0
    • affected 8.11.1
    • affected 8.11.0
    • affected 8.10.1
    • affected 8.10.0
    • affected 8.9.1
    • affected 8.9.0
    • affected 8.8.0
    • affected 8.7.1
    • affected 8.7.0
    • affected 8.6.0
    • affected 8.5.0
    • affected 8.4.0
    • affected 8.3.0
    • affected 8.2.1
    • affected 8.2.0
    • affected 8.1.2
    • affected 8.1.1
    • affected 8.1.0
    • affected 8.0.1
    • affected 8.0.0
    • affected 7.88.1
    • affected 7.88.0
    • affected 7.87.0
    • affected 7.86.0
    • affected 7.85.0
    • affected 7.84.0
    • affected 7.83.1
    • affected 7.83.0
    • affected 7.82.0
    • and 153 more

References

References3

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-8932 badge
[![CVE-2026-8932](https://cveledger.app/badge/CVE-2026-8932.svg)](https://cveledger.app/cve/CVE-2026-8932)

Record last updated .