# CVE-2026-91986: gitoxide gix-transport before 0.59.2 CR/LF/NUL Injection

> Attackers can inject control characters into git-daemon requests via crafted URLs, potentially spoofing virtual hosts or corrupting logs.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/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:** 15 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** AZL-103263, AZL-103266, DEBIAN-CVE-2026-91986, GHSA-7849-h6h3-vww8, GHSA-rc7h-wp5f-w3g5, UBUNTU-CVE-2026-91986, openSUSE-SU-2026:11857-1, openSUSE-SU-2026:21955-1, openSUSE-SU-2026:22126-1

## What is CVE-2026-91986?

CVE-2026-91986 is a medium-severity vulnerability in GitoxideLabs gitoxide, published on 15 Sep 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 gix-transport before 0.59.2 fails to filter control characters in git-daemon connect requests, allowing attackers to inject NUL/CR/LF bytes via crafted git URLs. Attackers can inject extra NUL-delimited protocol fields to spoof virtual hosts or inject newlines into daemon requests and logs.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gitoxide` | openSUSE:Leap 16.0 | All versions | 0.56.0-bp160.2.1 |
| `gitoxide` | openSUSE:Leap 16.0 | All versions | 0.60.0-bp160.1.1 |
| `gitoxide` | openSUSE:Tumbleweed | All versions | 0.58.0-2.1 |

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

Upgrade to a fixed version.

## Is CVE-2026-91986 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-91986 is a medium-severity vulnerability in GitoxideLabs gitoxide, published on 15 Sep 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-91986 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-91986/ (Markdown: https://insights.sbomify.com/CVE-2026-91986/index.md)
```

## Sources

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

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