gitoxide before 0.52.1 Repository Boundary Violation via symlinked .gitmodules (CVE-2026-82252) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-82252

gitoxide before 0.52.1 Repository Boundary Violation via symlinked .gitmodules

Answer in brief

CVE-2026-82252 records a Unknown severity vulnerability in gitoxide before 0.52.1 Repository Boundary Violation via symlinked .gitmodules. The current sources do not mark it as known exploited. The current feed maps GitoxideLabs/gitoxide (generic), GitoxideLabs/gitoxide (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 28, 2026Updated Aug 28, 2026Source checked Aug 28, 2026First seen by HOL Aug 28, 2026Material review Aug 28, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps GitoxideLabs/gitoxide (generic), GitoxideLabs/gitoxide (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
GitoxideLabs/gitoxidegeneric	>=0 <0.52.1	0.52.1
GitoxideLabs/gitoxidegeneric	>=0 <0.82	0.82

Recommended response

Check inventory. Check lockfiles and deployed manifests for GitoxideLabs/gitoxide, GitoxideLabs/gitoxide.
Review the reported fix. Update GitoxideLabs/gitoxide to 0.52.1; GitoxideLabs/gitoxide to 0.82 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 28, 2026

Sources and claim methodology

Upstream source description

gitoxide before 0.52.1 follows symlinks when reading the worktree .gitmodules file, allowing attackers to inject out-of-repository bytes into submodule metadata. Attackers can create a malicious repository with a symlinked .gitmodules pointing outside the repository tree, causing gitoxide to parse arbitrary external files as submodule configuration and expose attacker-controlled name, path, and url values.

Quoted source text, attributed separately from HOL analysis.