CVE-2026-94265: Authorization: Negotiate sent to foreign origin
Authorization: Negotiate sent to foreign origin
Other sources
When processing an HTTP redirect to a URL containing userinfo (a username:password component), curl might erroneously retain and re-transmit the original host's HTTP Negotiate authentication state. Consequently, a malicious server can trigger a redirect containing arbitrary userinfo to force curl to send a freshly minted Kerberos ticket—generated using the ambient identity of the client process to an untrusted third-party host, effectively bypassing the domain-scoping restrictions normally enforced by the absence of --location-trusted.
— NVD
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
alpine/curlto a version that resolves this vulnerability.Fixed in 8.23.0-r0 - Upgrade
Upgrade
debian/curlto a version that resolves this vulnerability.Fixed in 8.23.0~rc2-1 - Upgrade
Upgrade
debian/curlto a version that resolves this vulnerability.Fixed in 7.88.1-10+deb12u15Fixed in 7.88.1-10+deb12u5Fixed in 8.14.1-2+deb13u5Fixed in 8.14.1-2+deb13u7Fixed in 8.23.0-2Fixed in 8.24.0~rc1-1 - Upgrade
Upgrade
curlto a version that resolves this vulnerability.Fixed in 8.23.0 - Compensating control
Do not follow redirects when using Negotiate authentication.
Event History
Frequently Asked Questions
Who is exposed to this issue?
curl clients that process redirects from a server and have an ambient Kerberos identity are exposed when the redirect points to an untrusted third-party host and includes userinfo. The issue can cause a newly generated Kerberos ticket to be sent to that third party.
What must an attacker control to exploit it?
An attacker needs to cause curl to process an HTTP redirect to a URL containing arbitrary username:password userinfo, with the redirect targeting a host controlled by or trusted by the attacker. The client must have HTTP Negotiate authentication state for the original host.
Does avoiding --location-trusted prevent this disclosure?
No. The described behavior bypasses the domain-scoping restrictions that normally result from not using --location-trusted.