Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.7

gix and gitoxide: unvalidated submodule name traverses out of .git/modules and redirects state() / open() to another repository

GHSA-fr8x-3vfx-f45h

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (gix 0.83.0; gitoxide 0.52.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • crates.io gix

    Affected
    < 0.83.0
    Fixed in
    0.83.0

  • crates.io gitoxide

    Affected
    <= 0.52.0
    Fixed in
    0.52.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
7.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/E:P · score source
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Summary attachments: pocs.zip Submodule names coming from .gitmodules are exposed as unvalidated names and are later reused to derive the submodule git directory as: Because the submodule name is joined directly as a filesystem path component, a name such as ../../../escaped-target.git escapes .git/modules after normalization. The current implementation then uses that escaped path in both state() and open(). The updated PoC demonstrates the real sink, not just string construction: - state() reports repositoryexists=true for the traversed path; - open() returns a repository whose normalized commondir() matches the attacker-chosen repository outside .git/modules. Root cause analysis The relevant flow is: 1. gix-submodule/src/access.rs exposes unvalidated submodule names from configuration. 2. gix/src/submodule/mod.rs derives the git directory by doing commondir().join("modules").join(name) with no confinement check. 3. gix/src/submodule/mod.rs uses that derived path during state…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-fr8x-3vfx-f45h

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-fr8x-3vfx-f45h

Advisory: gix and gitoxide: unvalidated submodule name traverses out of .git/modules and redirects state() / open() to another repository
IDs: GHSA-fr8x-3vfx-f45h
Record: https://patchnext.com/advisories/ghsa-fr8x-3vfx-f45h (revision 1, source checked 26 Oct 2026, 15:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: gix 0.83.0; gitoxide 0.52.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io gix: affected < 0.83.0; fixed in 0.83.0
- crates.io gitoxide: affected <= 0.52.0; fixed in 0.52.1

## Suggested inspection (read-only)
- crates.io gix: check the installed version with your package manager.
- crates.io gitoxide: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on gix, gitoxide.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-fr8x-3vfx-f45h (GitHub-reviewed advisory GHSA-fr8x-3vfx-f45h lists affected ranges: crates.io gitoxide >=0 =0 <0.83.0)

Commands are suggestions: review each one before running it.

Loading voting…