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 u…

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

1. Mar 11, 2026 · NIST NVD

   Detected

   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 or keywords, curl would pass on the bearer token set for the first host also to the second o

2. Sep 15, 2026 · NIST NVD

   Updated

   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 or keywords, curl would pass on the bearer token set for the first host also to the second o

Affected

• cpe haxx/curlversion unspecified

Sources

• CVE.orgVulnerability recordCVE-2026-3783

  Official CVE identifier

  cve.org
• NIST NVDVulnerability recordCVE-2026-3783

  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 .ne

  nvd.nist.gov

References

• Mailing List · openwall.com
• Patch · curl.se
• Vendor Advisory · curl.se
• Exploit · hackerone.com