gitoxide's gix-url crate (<= 0.32.0, fixed in 0.37.1) uses a hand-rolled URL parser that does not treat '?' or '#' as terminating the authority component, contrary to RFC 3986. As a consequence, gix-transport's HTTP redirect identity guard (can_reuse_identity) compares the wrong host and fails open. An attacker controlling a redirect response can craft a Location header of the form <attacker-authority>?@<original-authority> so that gitoxide sends the caller's HTTP Basic Authorization credentials to an unintended host. gix-transport is affected in versions <= 0.49.0 (fixed in 0.58.1).

The gitoxide Rust library's gix-url crate (versions <= 0.32.0) contains a hand-rolled URL parser that fails to treat '?' or '#' as terminators for the authority component, violating RFC 3986. This flaw causes the HTTP redirect identity guard (can_reuse_identity) in gix-transport to compare incorrect host values, effectively failing open. An attacker who can control HTTP redirect responses can craft a malicious Location header in the form <attacker-authority>?@<original-authority> to trick gitoxide into sending HTTP Basic Authorization credentials to an unintended host. The vulnerability affects gix-transport versions <= 0.49.0. Fixes are available in gix-url 0.37.1 and gix-transport 0.58.1. This is a credential leakage vulnerability that could allow man-in-the-middle or redirect-based credential harvesting attacks against users of gitoxide for git operations over HTTP.