gix-transport: HTTP credentials leaked to redirected host in curl backend

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.8 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary The curl-based HTTP transport in gix-transport sends user credentials (passwords, tokens) to an attacker-controlled server after an HTTP redirect. When a server responds with a 302 redirect during the initial GET /info/refs, gitoxide records the redirected base URL and rewrites all subsequent requests to point at the redirected host. The Authorization header is still attached because addbasicauthifpresent() only checks self.url (the original, never-updated URL). The reqwest backend is not affected. Its custom redirect policy at reqwest/remote.rs lines 60-64 compares prevurl.hoststr() to currurl.hoststr() and calls attempt.stop() on cross-domain redirects, so redirectedbaseurl is never set to a different host. Details The vulnerability involves two components in gix-transport: 1. URL rewriting after redirect (gix-transport/src/client/blockingio/http/curl/remote.rs) After a request completes, the effective URL is compared to the requested URL. If they differ (redirect…

Published by the source

5 May 2026, 19:16 UTC

Last modified by the source

5 May 2026, 19:16 UTC

Source last checked

26 Oct 2026, 15:42 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-9857-6mw7-fq2m

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-9857-6mw7-fq2m

Advisory: gix-transport: HTTP credentials leaked to redirected host in curl backend
IDs: GHSA-9857-6mw7-fq2m
Record: https://patchnext.com/advisories/ghsa-9857-6mw7-fq2m (revision 1, source checked 26 Oct 2026, 15:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: gix-transport 0.56.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io gix-transport: affected >= 0.25.4, <= 0.55.0; fixed in 0.56.0

## Suggested inspection (read-only)
- crates.io gix-transport: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on gix-transport.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-9857-6mw7-fq2m (GitHub-reviewed advisory GHSA-9857-6mw7-fq2m lists affected ranges: crates.io gix-transport >=0.25.4 <=0.55.0)

Commands are suggestions: review each one before running it.