curl -- Multiple vulnerabiltiesentered 2026-03-11
no CVE referenced
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.
| Port | Package | Version | Status | Maintainer |
|---|---|---|---|---|
| ftp/linux-rl9-curl | linux-rl9-curl | 7.76.1_13 | unaddressed | emulation@FreeBSD.org |
no CVE referenced
Range taken from the CVE record, check it before committing. make newentry in security/vuxml creates the vid.
<vuln vid="FIXME (make newentry)">
<topic>FIXME -- FIXME</topic>
<affects>
<package>
<name>linux-rl9-curl</name>
<range><lt>8.19.0</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>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.</p>
</body>
</description>
<references>
<cvename>CVE-2026-3783</cvename>
<url>https://nvd.nist.gov/vuln/detail/CVE-2026-3783</url>
</references>
<dates>
<discovery>2026-03-11</discovery>
<entry>2026-10-25</entry>
</dates>
</vuln>