# CVE-2026-82255: gitoxide 0.25.4 HTTP Credential Leak via Redirect

> Attackers can steal authentication tokens by exploiting HTTP redirects in gitoxide, leading to credential exposure and potential account takeover.

- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 28 Aug 2026
- **Updated:** 30 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-82255, GHSA-2r3q-w7g9-8rpr, GHSA-9857-6mw7-fq2m, MINI-j3p4-f6j8-hc2q, UBUNTU-CVE-2026-82255

## What is CVE-2026-82255?

CVE-2026-82255 is a high-severity vulnerability in GitoxideLabs gitoxide, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

gitoxide versions from 0.25.4 contain an HTTP credential leak vulnerability in the curl-based transport backend where credentials are sent to attacker-controlled servers after HTTP redirects. The vulnerability occurs because credential validation checks the original URL instead of the effective URL after redirect, allowing attackers to steal authentication tokens through cross-domain redirects or HTTPS-to-HTTP downgrades.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2026-82255?

2 open source packages ship an affected version, including gix-transport.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gix-transport` | crates.io | From 0.25.4 | 0.56.0 |
| `gix-transport` | crates.io | From 0.25.4 | 0.56.0 |

## How do I fix CVE-2026-82255?

Upgrade gix-transport to 0.56.0 or later.

## Is CVE-2026-82255 being exploited?

There is no known exploitation of CVE-2026-82255 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-82255 and fix it if it is affected.

What it is: CVE-2026-82255 is a high-severity vulnerability in GitoxideLabs gitoxide, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-82255 in the wild and no public exploit code.

Affected packages and fixed versions:
- gix-transport (crates.io): affected from 0.25.4; fixed in 0.56.0
- gix-transport (crates.io): affected from 0.25.4; fixed in 0.56.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-82255/ (Markdown: https://insights.sbomify.com/CVE-2026-82255/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-82255
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-82255
- OSV: https://osv.dev/vulnerability/CVE-2026-82255

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-82255/
Summaries are generated and may contain mistakes; the official description above is the record.