Git vulnerable to local clone-based data exfiltration with non-local transports

Summary

Git is a revision control system. Using a specially-crafted repository, Git prior to versions 2.39.2, 2.38.4, 2.37.6, 2.36.5, 2.35.7, 2.34.7, 2.33.7, 2.32.6, 2.31.7, and 2.30.8 can be tricked into using its local clone optimization even when using a non-local transport. Though Git will abort local clones whose source `$GIT_DIR/objects` directory contains symbolic links, the `objects` directory itself may still be a symbolic link. These two may be combined to include arbitrary files based on known paths on the victim's filesystem within the malicious repository's working copy, allowing for data exfiltration in a similar manner as CVE-2022-39253. A fix has been prepared and will appear in v2.39.2 v2.38.4 v2.37.6 v2.36.5 v2.35.7 v2.34.7 v2.33.7 v2.32.6, v2.31.7 and v2.30.8. If upgrading is impractical, two short-term workarounds are available. Avoid cloning repositories from untrusted sources with `--recurse-submodules`. Instead, consider cloning repositories without recursively cloning their submodules, and instead run `git submodule update` at each layer. Before doing so, inspect each new `.gitmodules` file to ensure that it does not contain suspicious module URLs.

Timeline

1. Feb 14, 2023, 7:47 PM UTCCVE published
2. Oct 8, 2026, 9:12 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: partial

3. Oct 8, 2026, 9:14 PM UTCRecord last updated

Affected versions

• git git

  From 2.39.0 · fixed in 2.39.2; From 2.38.0 · fixed in 2.38.4; From 2.37.0 · fixed in 2.37.6; From 2.36.0 · fixed in 2.36.5; From 2.35.0 · fixed in 2.35.7; From 2.34.0 · fixed in 2.34.7; From 2.33.0 · fixed in 2.33.7; From 2.32.0 · fixed in 2.32.6; From 2.31.0 · fixed in 2.31.7; fixed in 2.30.8

References 4