# CVE-2026-82249: gitoxide before 0.38.2 Credential Helper Protocol Field Injection

> Attackers can inject carriage returns into URLs to trick credential helpers into leaking credentials for attacker-controlled hosts.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:L/VI:N/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:** 28 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-82249, GHSA-6wr8-3w4h-j9wj, GHSA-m78c-xpg9-p5ww, UBUNTU-CVE-2026-82249

## What is CVE-2026-82249?

CVE-2026-82249 is a low-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 before 0.38.2 fails to validate carriage return characters in URL values passed to credential helpers. Attackers can supply URLs containing bare carriage returns to inject additional helper protocol fields and cause credential helpers to return credentials for attacker-specified hosts instead of the requested URL.

Weakness: CWE-116 (Improper Encoding or Escaping of Output)

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


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

Upgrade to a fixed version.

## Is CVE-2026-82249 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82249 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82249 is a low-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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82249 exists.

Affected product: GitoxideLabs gitoxide. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-82249/ (Markdown: https://insights.sbomify.com/CVE-2026-82249/index.md)
```

## Sources

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

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