CVE-2026-71556: go-git: Worktree operations may follow symlinks
Impact A symlink traversal issue in go-git could allow worktree operations to modify files outside the intended worktree path. The worktreeFilesystem wrapper rejected dangerous path strings, including paths containing .git, parent-directory components, or control characters. However, it did not prevent filesystem operations from following symbolic links that were already present in the worktree.
Published Aug 7, 2026
Affected packages
github.com/go-git/go-git/v5
- Ecosystem
- Go
- Affected
- <= 5.19.1
- Fixed in
- 5.19.2
- Check
go list -m github.com/go-git/go-git/v5
github.com/go-git/go-git/v6
- Ecosystem
- Go
- Affected
- <= 6.0.0-alpha.4
- Fixed in
- 6.0.0-alpha.5
- Check
go list -m github.com/go-git/go-git/v6
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
A symlink traversal issue in go-git could allow worktree operations to modify files outside the intended worktree path.
The worktreeFilesystem wrapper rejected dangerous path strings, including paths containing .git, parent-directory components, or control characters. However, it did not prevent filesystem operations from following symbolic links that were already present in the worktree.
As a result, a path that is safe when evaluated as a string could still resolve into the repository's Git metadata directory. For example, if s is a symbolic link to .git, writing to s/config would modify .git/config.
A symbolic link at the final path component could also be followed. For example, if s points directly to .git/config, opening s for writing with truncation could overwrite the repository configuration.
Exploitation requires an attacker to be able to introduce or control a symbolic link in the worktree and cause the application to perform a write through that path.
Applications using storage/memory for their Storer, or go-billy/memfs for their Worktree, are not affected by this vulnerability.
Patches
The issue has been addressed by making the worktree filesystem wrapper a symlink-safe boundary.
Worktree operations now reject paths where an existing symbolic link in any path component could cause the operation to escape the intended worktree location, including symbolic links at the final component.
Users of filesystem-backed worktrees should upgrade to a patched version.
Credits
Thanks to @kodareef5 for reporting this issue and working with the go-git security team toward its resolution. :1st_place_medal: We would also like to thank @HughLewis20, who independently reported the same issue while a fix was already in progress.
Credited to kodareef5, HughLewis20.
References
- https://github.com/go-git/go-git/security/advisories/GHSA-hc8v-wwc9-vgxm
- https://github.com/go-git/go-git/commit/008a78f2dd86f52544ddff8b8e8ddeecdf3f7aab
- https://github.com/go-git/go-git/commit/661d1c7f101d34e002a3cfcf8dbea5b7421d07ac
- https://github.com/go-git/go-git/releases/tag/v5.19.2
- https://github.com/go-git/go-git/releases/tag/v6.0.0-alpha.5
- https://github.com/advisories/GHSA-hc8v-wwc9-vgxm
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-71557
go-git: Malicious reference names may modify files outside the reference storage
medium6.3Aug 7, 2026GHSA-w5pp-99ch-qj29
go-git: Malformed Git object data may cause panics or resource exhaustion
medium6.5May 29, 2026CVE-2026-45570
go-git: Improper single-quote escaping in go-git SSH transport
low2.3No fixMay 19, 2026CVE-2026-45571
go-git: Crafted repositories may modify main and submodule .git directories
medium5.4No fixMay 19, 2026CVE-2026-45022
go-git's improper parsing of specially crafted objects may lead to inconsistent interpretation compared to upstream Git
high7.0May 11, 2026CVE-2026-41506
go-git: Credential leak via cross-host redirect in smart HTTP transport
medium4.7Apr 17, 2026
