curl libcurl up to 8.21.0/8.22.0 Connection Cache match insertion of sensitive information into sent data
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 1.28 |
Summary
A vulnerability categorized as problematic has been discovered in curl libcurl up to 8.21.0/8.22.0. Affected is the function Match of the component Connection Cache. Executing a manipulation can lead to insertion of sensitive information into sent data.
The identification of this vulnerability is CVE-2026-86415. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability has been found in curl libcurl up to 8.21.0/8.22.0 and classified as problematic. This vulnerability affects the function match of the component Connection Cache. The manipulation with an unknown input leads to a insertion of sensitive information into sent data vulnerability. The CWE definition for the vulnerability is CWE-201. The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor. As an impact it is known to affect confidentiality. CVE summarizes:
libcurl's connection cache match function never considers the automatic client certificate option, so a cached, already authenticated Schannel connection can be handed to a transfer that got redirected to a different origin, even though the code explicitly switched off the auto client cert option for that transfer to prevent exactly this.
The advisory is shared for download at curl.se. This vulnerability was named CVE-2026-86415 since 09/07/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 10/20/2026). The MITRE ATT&CK project declares the attack technique as T1592.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Insertion of sensitive information into sent dataCWE: CWE-201 / CWE-200 / CWE-284
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
09/07/2026 CVE reserved10/20/2026 Advisory disclosed
10/20/2026 VulDB entry created
10/20/2026 VulDB entry last update
Sources
Advisory: curl.seStatus: Confirmed
CVE: CVE-2026-86415 (🔒)
GCVE (CVE): GCVE-0-2026-86415
GCVE (VulDB): GCVE-100-423004
Entry
Created: 10/20/2026 22:48Changes: 10/20/2026 22:48 (54)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.