Monitor vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
5.3
Curl Exposes OAuth Tokens with Redirection and .netrc
CVE-2026-3783
CURL-CVE-2026-3783
Summary
A security risk exists when using OAuth tokens with curl and .netrc files. If a redirect occurs during an HTTPS transfer, the token may be leaked to the new host. To prevent this, ensure that .netrc files do not contain sensitive information, and consider disabling .netrc support in curl.
What to do
No fix is available yet. Check with your software vendor for updates.
Affected software
| Vendor | Product | Affected versions | Fix available |
|---|---|---|---|
| haxx | curl | > 7.33.0 , <= 8.19.0 | – |
Original title
token leak with redirect and netrc
Original description
When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer
performs a redirect to a second URL, curl could leak that token to the second
hostname under some circumstances.
If the hostname that the first request is redirected to has information in the
used .netrc file, with either of the `machine` or `default` keywords, curl
would pass on the bearer token set for the first host also to the second one.
performs a redirect to a second URL, curl could leak that token to the second
hostname under some circumstances.
If the hostname that the first request is redirected to has information in the
used .netrc file, with either of the `machine` or `default` keywords, curl
would pass on the bearer token set for the first host also to the second one.
Vulnerability type
CWE-522
Insufficiently Protected Credentials
Published: 11 Mar 2026 · Updated: 14 Mar 2026 · First seen: 11 Mar 2026