CVE-2026-8458: wrong reuse for different services
Vendor fix available · Affected: curl · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 31% of scored CVEs
DescriptionCVE.org
libcurl might in some circumstances reuse the wrong connection when asked to do Negotiate-authenticated ones, even when they are set to use different "services". libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead. When reusing a connection a range of criteria must be met. Due to a logical error in the code, a request that was issued by an application could wrongfully reuse an existing connection to the same server that was authenticated using different services.
Affected products3
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- curl · curlfrom 7.43.0 before 8.14.2; from 8.15.0 before 8.16.1; from 8.17.0 before 8.20.1
- curl · curlVersions not stated
- curl · curl8.20.0; 8.19.0; 8.18.0; 8.17.0; 8.16.0; 8.15.0 and 92 more
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- curl
- Published
- July 2026
- Bounty reports
- 1 disclosed on HackerOne
Disclosed bug bounty reports about CVE-2026-8458
The reports on HackerOne that name this CVE, with HackerOne's own outcome. Titles and metadata only.
- CVE-2026-8458: wrong reuse for different servicescurl · 2026 · low severityValid
CoverageNo articles yet
No CyberSIXT article names CVE-2026-8458 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.