CVE-2026-3783: token leak with redirect and netrc
token leak with redirect and netrc
Other sources
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.
— MITRE
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2026-3783?
CVE-2026-3783 is considered a moderate severity vulnerability due to the potential leakage of OAuth2 bearer tokens during HTTP(S) redirects.
How do I fix CVE-2026-3783?
To mitigate CVE-2026-3783, users should upgrade to the latest version of curl that addresses this vulnerability.
What kind of information could be leaked due to CVE-2026-3783?
CVE-2026-3783 may lead to the exposure of sensitive OAuth2 bearer tokens to unintended third-party hosts.
Which software is affected by CVE-2026-3783?
CVE-2026-3783 primarily affects redhat/curl versions prior to the fix for this vulnerability.
How can the token leak in CVE-2026-3783 happen?
The token leak in CVE-2026-3783 occurs when curl performs a redirect after using an OAuth2 bearer token for an HTTP(S) transfer.