Repository integrity bypass via unchecked SHA-1 collisions
Published Apr 4, 2025 · Updated Jan 23, 2026
Weak SHA-1 hashing in GitoxideLabs gitoxide before 0.42.0 allows remote attackers to substitute distinct Git objects with the same hash. The gix-features hash layer delegates Git object hashing to sha1_smol or sha1, which returns ordinary SHA-1 digests without collision checks. Exploitation requires a computationally costly SHA-1 collision and can disguise malicious repository contents or violate downstream integrity assumptions.
Summary
What happened
Weak SHA-1 hashing in GitoxideLabs gitoxide before 0.42.0 allows remote attackers to substitute distinct Git objects with the same hash. The gix-features hash layer delegates Git object hashing to sha1_smol or sha1, which returns ordinary SHA-1 digests without collision checks. Exploitation requires a computationally costly SHA-1 collision and can disguise malicious repository contents or violate downstream integrity assumptions.
The record
- CVE
- CVE-2025-31130
- Published
- Apr 4, 2025
- Updated
- Jan 23, 2026
- Vendor
- GitoxideLabs
- Product
- gitoxide
- Classifications
- CWE-328, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 4, 2025CVE publishedPublication date reported by the CVE source.
- Jan 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.42.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- GHSA-2frx-2596-x5r6 SHA-1 collision demonstrationproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo