cURL up to 8.20.0 Proxy Configuration authentication replay
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.7 | $0-$5k | 1.50 |
Summary
A vulnerability was found in cURL. It has been classified as problematic. Impacted is an unknown function of the component Proxy Configuration Handler. The manipulation leads to authentication replay. This vulnerability is listed as CVE-2026-8927. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in cURL. It has been rated as problematic. This issue affects an unknown code block of the component Proxy Configuration Handler. The manipulation with an unknown input leads to a authentication replay vulnerability. Using CWE to declare the problem leads to CWE-294. A capture-replay flaw exists when the design of the product makes it possible for a malicious user to sniff network traffic and bypass authentication by replaying it to the server in question to the same effect as the original message (or with minor changes). Impacted is integrity. The summary by CVE is:
When reusing a libcurl handle for sequential transfers driven by environment-variable proxy configuration, libcurl fails to clear the proxy authentication state between requests. Specifically, if the initial transfer authenticates against `proxyA` using Digest auth, a subsequent transfer routed through `proxyB` erroneously leaks the `Proxy-Authorization:` header intended solely for `proxyA`.
The weakness was presented by Ady Elouej. The advisory is shared at curl.se. The identification of this vulnerability is CVE-2026-8927 since 05/19/2026. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/03/2026). MITRE ATT&CK project uses the attack technique T1040 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-41508). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
- 7.0
- 7.1
- 7.2
- 7.3
- 7.4
- 7.5
- 7.6
- 7.7
- 7.8
- 7.9
- 7.10
- 7.11
- 7.12
- 7.12.0
- 7.12.1
- 7.12.2
- 7.12.3
- 7.13
- 7.13.0
- 7.13.1
- 7.13.2
- 7.14
- 7.14.0
- 7.14.1
- 7.15
- 7.15.0
- 7.15.1
- 7.15.2
- 7.15.3
- 7.15.4
- 7.15.5
- 7.16
- 7.16.0
- 7.16.1
- 7.16.2
- 7.16.3
- 7.16.4
- 7.17
- 7.17.0
- 7.17.1
- 7.18
- 7.18.0
- 7.18.1
- 7.18.2
- 7.19
- 7.19.0
- 7.19.1
- 7.19.2
- 7.19.3
- 7.19.4
- 7.19.5
- 7.19.6
- 7.19.7
- 7.20
- 7.20.0
- 7.20.1
- 7.21
- 7.21.0
- 7.21.1
- 7.21.2
- 7.21.3
- 7.21.4
- 7.21.5
- 7.21.6
- 7.21.7
- 7.22
- 7.22.0
- 7.23
- 7.23.0
- 7.23.1
- 7.24
- 7.24.0
- 7.25
- 7.25.0
- 7.26
- 7.26.0
- 7.27
- 7.27.0
- 7.28
- 7.28.0
- 7.28.1
- 7.29
- 7.29.0
- 7.30
- 7.30.0
- 7.31
- 7.31.0
- 7.32
- 7.32.0
- 7.33
- 7.33.0
- 7.34
- 7.34.0
- 7.35
- 7.35.0
- 7.36
- 7.36.0
- 7.37
- 7.37.0
- 7.37.1
- 7.38
- 7.38.0
- 7.39
- 7.39.0
- 7.40
- 7.40.0
- 7.41
- 7.41.0
- 7.42
- 7.42.0
- 7.42.1
- 7.43
- 7.43.0
- 7.44
- 7.44.0
- 7.45
- 7.45.0
- 7.46
- 7.46.0
- 7.47
- 7.47.0
- 7.47.1
- 7.48
- 7.48.0
- 7.49
- 7.49.0
- 7.49.1
- 7.50
- 7.50.0
- 7.50.1
- 7.50.2
- 7.50.3
- 7.51
- 7.51.0
- 7.52
- 7.52.0
- 7.52.1
- 7.53
- 7.53.0
- 7.53.1
- 7.54
- 7.54.0
- 7.54.1
- 7.55
- 7.55.0
- 7.55.1
- 7.56
- 7.56.0
- 7.56.1
- 7.57
- 7.57.0
- 7.58
- 7.58.0
- 7.59
- 7.59.0
- 7.60
- 7.60.0
- 7.61
- 7.61.0
- 7.61.1
- 7.62
- 7.62.0
- 7.63
- 7.63.0
- 7.64
- 7.64.0
- 7.64.1
- 7.65
- 7.65.0
- 7.65.1
- 7.65.2
- 7.65.3
- 7.66
- 7.66.0
- 7.67
- 7.67.0
- 7.68
- 7.68.0
- 7.69
- 7.69.0
- 7.69.1
- 7.70
- 7.70.0
- 7.71
- 7.71.0
- 7.71.1
- 7.72
- 7.72.0
- 7.73
- 7.73.0
- 7.74
- 7.74.0
- 7.75
- 7.75.0
- 7.76
- 7.76.0
- 7.76.1
- 7.77
- 7.77.0
- 7.78
- 7.78.0
- 7.79
- 7.79.0
- 7.79.1
- 7.80
- 7.80.0
- 7.81
- 7.81.0
- 7.82
- 7.82.0
- 7.83
- 7.83.0
- 7.83.1
- 7.84
- 7.84.0
- 7.85
- 7.85.0
- 7.86
- 7.86.0
- 7.87
- 7.87.0
- 7.88.0
- 7.88.1
- 8.0
- 8.0.0
- 8.0.1
- 8.1
- 8.1.0
- 8.1.1
- 8.1.2
- 8.2
- 8.2.0
- 8.2.1
- 8.3
- 8.3.0
- 8.4
- 8.4.0
- 8.5
- 8.5.0
- 8.6
- 8.6.0
- 8.7
- 8.7.0
- 8.7.1
- 8.8
- 8.8.0
- 8.9
- 8.9.0
- 8.9.1
- 8.10
- 8.10.0
- 8.10.1
- 8.11
- 8.11.0
- 8.11.1
- 8.12
- 8.12.0
- 8.12.1
- 8.13
- 8.13.0
- 8.14
- 8.14.0
- 8.14.1
- 8.15
- 8.15.0
- 8.16
- 8.16.0
- 8.17
- 8.17.0
- 8.18
- 8.18.0
- 8.19
- 8.19.0
- 8.20.0
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.7VulDB Meta Temp Score: 3.7
VulDB Base Score: 3.7
VulDB Temp Score: 3.7
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: Authentication replayCWE: CWE-294 / CWE-287
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
05/19/2026 CVE reserved07/03/2026 Advisory disclosed
07/03/2026 VulDB entry created
07/03/2026 VulDB entry last update
Sources
Advisory: curl.seResearcher: Ady Elouej
Status: Confirmed
CVE: CVE-2026-8927 (🔒)
GCVE (CVE): GCVE-0-2026-8927
GCVE (VulDB): GCVE-100-376073
EUVD: 🔒
Entry
Created: 07/03/2026 08:58Updated: 07/03/2026 14:19
Changes: 07/03/2026 08:58 (54), 07/03/2026 14:19 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.