gitoxide does not detect SHA-1 collision attacks

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.8 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N

EPSS

• CVE-2025-31130: 0.26% estimated exploitation activity in the next 30 days; percentile 17.98 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary gitoxide uses SHA-1 hash implementations without any collision detection, leaving it vulnerable to hash collision attacks. Details gitoxide uses the sha1smol or sha1 crate, both of which implement standard SHA-1 without any mitigations for collision attacks. This means that two distinct Git objects with colliding SHA-1 hashes would break the Git object model and integrity checks when used with gitoxide. The SHA-1 function is considered cryptographically insecure. However, in the wake of the SHAttered attacks, this issue was mitigated in Git 2.13.0 in 2017 by using the sha1collisiondetection algorithm by default and producing an error when known SHA-1 collisions are detected. Git is in the process of migrating to using SHA-256 for object hashes, but this has not been rolled out widely yet and gitoxide does not support SHA-256 object hashes. PoC The following program demonstrates the problem, using the two SHAttered PDFs: The output is as follows: The latter behaviour matches…

Published by the source

4 Apr 2025, 16:06 UTC

Last modified by the source

23 Jan 2026, 17:09 UTC

Source last checked

26 Oct 2026, 15:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-2frx-2596-x5r6

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

# Patch Next advisory brief: CVE-2025-31130

Advisory: gitoxide does not detect SHA-1 collision attacks
IDs: CVE-2025-31130, GHSA-2frx-2596-x5r6
Record: https://patchnext.com/advisories/cve-2025-31130 (revision 1, source checked 26 Oct 2026, 15:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: gix-odb 0.68.0; gix 0.71.0; gix-pack 0.58.0; gix-archive 0.20.0; gix-merge 0.4.0; gix-index 0.39.0; gix-negotiate 0.19.0; gix-discover 0.39.0; gix-object 0.48.0; gix-fsck 0.10.0; gix-config 0.44.0; gix-traverse 0.45.0; gix-blame 0.1.0; gitoxide 0.42.0; gix-revision 0.33.0; gix-filter 0.18.0; gix-features 0.41.0; gitoxide-core 0.46.0; gix-diff 0.51.0; gix-revwalk 0.19.0; gix-worktree 0.40.0; gix-dir 0.13.0; gix-worktree-state 0.18.0; gix-ref 0.51.0; gix-commitgraph 0.27.0; gix-status 0.18.0; gix-protocol 0.49.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io gix-odb: affected < 0.68.0; fixed in 0.68.0
- crates.io gix: affected < 0.71.0; fixed in 0.71.0
- crates.io gix-pack: affected < 0.58.0; fixed in 0.58.0
- crates.io gix-archive: affected < 0.20.0; fixed in 0.20.0
- crates.io gix-merge: affected < 0.4.0; fixed in 0.4.0
- crates.io gix-index: affected < 0.39.0; fixed in 0.39.0
- crates.io gix-negotiate: affected < 0.19.0; fixed in 0.19.0
- crates.io gix-discover: affected < 0.39.0; fixed in 0.39.0
- crates.io gix-object: affected < 0.48.0; fixed in 0.48.0
- crates.io gix-fsck: affected < 0.10.0; fixed in 0.10.0
- crates.io gix-config: affected < 0.44.0; fixed in 0.44.0
- crates.io gix-traverse: affected < 0.45.0; fixed in 0.45.0
- crates.io gix-blame: affected < 0.1.0; fixed in 0.1.0
- crates.io gitoxide: affected < 0.42.0; fixed in 0.42.0
- crates.io gix-revision: affected < 0.33.0; fixed in 0.33.0
- crates.io gix-filter: affected < 0.18.0; fixed in 0.18.0
- crates.io gix-features: affected < 0.41.0; fixed in 0.41.0
- crates.io gitoxide-core: affected < 0.46.0; fixed in 0.46.0
- crates.io gix-diff: affected < 0.51.0; fixed in 0.51.0
- crates.io gix-revwalk: affected < 0.19.0; fixed in 0.19.0
- crates.io gix-worktree: affected < 0.40.0; fixed in 0.40.0
- crates.io gix-dir: affected < 0.13.0; fixed in 0.13.0
- crates.io gix-worktree-state: affected < 0.18.0; fixed in 0.18.0
- crates.io gix-ref: affected < 0.51.0; fixed in 0.51.0
- crates.io gix-commitgraph: affected < 0.27.0; fixed in 0.27.0
- crates.io gix-status: affected < 0.18.0; fixed in 0.18.0
- crates.io gix-protocol: affected < 0.49.0; fixed in 0.49.0

## Suggested inspection (read-only)
- crates.io gix-odb: check the installed version with your package manager.
- crates.io gix: check the installed version with your package manager.
- crates.io gix-pack: check the installed version with your package manager.
- crates.io gix-archive: check the installed version with your package manager.
- crates.io gix-merge: check the installed version with your package manager.
- crates.io gix-index: check the installed version with your package manager.
- crates.io gix-negotiate: check the installed version with your package manager.
- crates.io gix-discover: check the installed version with your package manager.
- crates.io gix-object: check the installed version with your package manager.
- crates.io gix-fsck: check the installed version with your package manager.
- crates.io gix-config: check the installed version with your package manager.
- crates.io gix-traverse: check the installed version with your package manager.
- crates.io gix-blame: check the installed version with your package manager.
- crates.io gitoxide: check the installed version with your package manager.
- crates.io gix-revision: check the installed version with your package manager.
- crates.io gix-filter: check the installed version with your package manager.
- crates.io gix-features: check the installed version with your package manager.
- crates.io gitoxide-core: check the installed version with your package manager.
- crates.io gix-diff: check the installed version with your package manager.
- crates.io gix-revwalk: check the installed version with your package manager.
- crates.io gix-worktree: check the installed version with your package manager.
- crates.io gix-dir: check the installed version with your package manager.
- crates.io gix-worktree-state: check the installed version with your package manager.
- crates.io gix-ref: check the installed version with your package manager.
- crates.io gix-commitgraph: check the installed version with your package manager.
- crates.io gix-status: check the installed version with your package manager.
- crates.io gix-protocol: 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-odb, gix, gix-pack, gix-archive, gix-merge, gix-index, gix-negotiate, gix-discover, gix-object, gix-fsck, gix-config, gix-traverse, gix-blame, gitoxide, gix-revision, gix-filter, gix-features, gitoxide-core, gix-diff, gix-revwalk, gix-worktree, gix-dir, gix-worktree-state, gix-ref, gix-commitgraph, gix-status, gix-protocol.
- 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-2frx-2596-x5r6 (GitHub-reviewed advisory GHSA-2frx-2596-x5r6 lists affected ranges: crates.io gix-features >=0 =0 =0 =0 =0 =0 =0 =0 =0 =0 =0 =0 =0…)

Commands are suggestions: review each one before running it.