CVE-2025-14524Published Jan 8, 2026 · Jan 8Updated Oct 28
bearer token leak on cross-protocol redirect
curl
Medium5.3Fix available
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| curl curl |
| No fix yet |
| curl curl |
| No fix yet |
| curl curl |
|
curl
| Product | Affected | Fixed in |
|---|---|---|
| curl curl |
| No fix yet |
| curl curl |
| No fix yet |
| curl curl |
|
8.16.08.15.08.14.18.14.08.13.0| No fix yet |
When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a cross-protocol redirect to a second URL that uses an IMAP, LDAP, POP3 or SMTP scheme, curl might wrongly pass on the bearer token to the new target host.
From the CVE record · curl
curl may pass an OAuth2 bearer token to a new host when an HTTP(S) transfer redirects to an IMAP, LDAP, POP3, or SMTP URL. This can expose the token to the redirect target when the transfer uses a bearer token and follows such a cross-protocol redirect.
Engineers running curl should check transfers that use OAuth2 bearer tokens; affected versions are not specified.