# CVE-2026-82248: gitoxide before 0.33.0 Path Traversal via symlink following

> Attackers can overwrite files outside the worktree on Windows via symlink following during incremental checkouts in Gitoxide.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:N/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:** No
- **Published:** 28 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-pmm9-4h7q-24c8, GHSA-r399-grgc-5vpp, UBUNTU-CVE-2026-82248

## What is CVE-2026-82248?

CVE-2026-82248 is a medium-severity path traversal 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

gix-worktree-state before 0.33.0 (part of gitoxide) allows writing files outside the worktree on Windows. gix_worktree_state::checkout() follows an existing terminal symlink during non-exclusive (incremental) materialization (destination_is_initially_empty: false) when core.symlinks is true. If a symlink entry (mode 120000) is first checked out at a path P pointing outside the worktree, a subsequent incremental checkout of a regular-file entry (mode 100644) at the same path follows the existing reparse point and writes the blob content through the link, overwriting files outside the worktree.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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


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

No fix has been published for CVE-2026-82248 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-82248 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82248 is a medium-severity path traversal 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-82248 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-82248/ (Markdown: https://insights.sbomify.com/CVE-2026-82248/index.md)
```

## Sources

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

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