CVE-2026-82248 GitoxideLabs CVE debrief

Who should care

Users of gitoxide and gix-worktree-state, especially those on Windows, should be aware of this vulnerability and take steps to mitigate it. This includes updating to version 0.33.0 or later of gix-worktree-state, reviewing symlink handling configurations, and monitoring file system changes for unexpected writes.

Technical summary

The gix-worktree-state crate before version 0.33.0, part of the gitoxide project, has a vulnerability that allows writing files outside the worktree on Windows. This occurs when the core.symlinks configuration is set to true and the gix_worktree_state::checkout() function follows an existing terminal symlink during non-exclusive (incremental) materialization. Specifically, if a symlink entry (mode 120000) is initially checked out at a path pointing outside the worktree, a subsequent incremental checkout of a regular-file entry (mode 100644) at the same path will follow the existing reparse point and write the blob content through the link. This can result in overwriting files outside the worktree.

Defensive priority

This vulnerability allows writing files outside the worktree on Windows when using gix-worktree-state before 0.33.0. Users should prioritize updating to version 0.33.0 or later to prevent potential security issues.

Recommended defensive actions

• Update gix-worktree-state to version 0.33.0 or later
• Review and adjust symlink handling configurations
• Monitor file system changes for unexpected writes
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The vulnerability exists in gix-worktree-state before 0.33.0, which is part of gitoxide. The issue arises when core.symlinks is true and gix_worktree_state::checkout() follows an existing terminal symlink during non-exclusive materialization. If a symlink entry is first checked out at a path pointing outside the worktree, a subsequent incremental checkout of a regular-file entry at the same path can write the blob content through the link, overwriting files outside the worktree.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.