# CVE-2026-82253: gitoxide before 0.82.0 Path Traversal via Submodule Name Validation Bypass

> Attackers can bypass submodule name validation to read arbitrary git configuration and credentials, bypassing safe-directory protections in applications using gitoxide.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/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:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** AZL-98409, AZL-98433, DEBIAN-CVE-2026-82253, GHSA-6f8q-f8px-cxhw, GHSA-p3hw-mv63-rf9w, MINI-938w-gq2h-v4gh, UBUNTU-CVE-2026-82253

## What is CVE-2026-82253?

CVE-2026-82253 is a high-severity path traversal vulnerability in GitoxideLabs gitoxide, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

gitoxide (Rust crates gix <= 0.72.0 and gix-validate <= 0.10.0) contains a path traversal vulnerability. The submodule name validation function in gix-validate only checks the first occurrence of '..' via name.find(b".."), allowing crafted names such as 'a..b/../../../.git/' to bypass the check; additionally this validation is never invoked in production code paths. Combined with a trust inheritance flaw in Submodule::open(), where the parent repository's git_dir_trust (Trust::Full) is cloned and the ownership verification is skipped, an attacker can craft a malicious .gitmodules file so that a victim tool built on gitoxide reads arbitrary git repository configuration (including embedded credentials) with full trust, bypassing safe-directory protections. Fixed in gix 0.82.0 and gix-validate 0.11.1.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

4 open source packages ship an affected version, including gix and gix-validate.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gix` | crates.io | All versions | 0.83.0 |
| `gix` | crates.io | All versions | 0.83.0 |
| `gix-validate` | crates.io | All versions | 0.11.1 |
| `gix-validate` | crates.io | All versions | 0.11.1 |

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

Upgrade gix to 0.83.0 or later.

## Is CVE-2026-82253 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82253 is a high-severity path traversal vulnerability in GitoxideLabs gitoxide, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82253 exists.

Affected packages and fixed versions:
- gix (crates.io): affected all versions; fixed in 0.83.0
- gix (crates.io): affected all versions; fixed in 0.83.0
- gix-validate (crates.io): affected all versions; fixed in 0.11.1
- gix-validate (crates.io): affected all versions; fixed in 0.11.1

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

## Sources

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

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