A redirect can cross the authentication boundary

CVE-2026-94265 concerns HTTP Negotiate authentication in curl. When a redirect points to a URL that contains user information, curl could retain and resend the original host’s authentication state. A malicious server could use this to make a client send a Kerberos ticket to another host.

The issue affects curl 8.21.0 through 8.22.0 and is fixed in 8.23.0. The curl project rates it Low. It applies to clients that use Negotiate authentication and follow redirects; other authentication modes do not automatically have the same path.

Check authenticated redirect workflows

Find applications that use Negotiate or ambient Kerberos credentials with libcurl. Review whether they follow redirects and whether the destination can be influenced by a server response or user input.

Use a fixed service origin where possible. Avoid enabling cross-origin credential forwarding unless the application has a documented need and a verified trust relationship.

Upgrade and validate the destination

Update curl and libcurl to 8.23.0 or a supported vendor build containing the fix. Restart the application and check the library loaded by its process.

Test a redirect to a different host in a controlled environment and confirm that authentication is not sent to that origin. Review the server logs if a credential leak is suspected.