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.
Metrics
Affected Vendors & Products
References
History
Wed, 11 Mar 2026 11:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Wed, 11 Mar 2026 10:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | token leak with redirect and netrc | |
| References |
|
Status: PUBLISHED
Assigner: curl
Published:
Updated: 2026-03-11T14:26:10.788Z
Reserved: 2026-03-08T05:09:09.891Z
Link: CVE-2026-3783
No data.
Status : Awaiting Analysis
Published: 2026-03-11T11:16:00.080
Modified: 2026-03-11T13:52:47.683
Link: CVE-2026-3783
No data.
OpenCVE Enrichment
No data.