go-git: Worktree operations may follow symlinks
Published 7 Aug 2026 · Updated 10 Sept 2026
Is your project on an affected github.com/go-git/go-git/v5?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- <5.19.2
- Fixed in
- 5.19.2
go get github.com/go-git/go-git/v5@v5.19.2- Affected
- <6.0.0-alpha.5
- Fixed in
- 6.0.0-alpha.5
go get github.com/go-git/go-git/v6@v6.0.0-alpha.5Details
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.
Is GHSA-hc8v-wwc9-vgxm in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/go-git/go-git/v5, and gives you the command that fixes it.
More advisories for github.com/go-git/go-git/v5
- LowCVE-2026-71557Path traversal via crafted reference names in github.com/go-git/go-git · 18 Aug 2026
- MediumCVE-2026-71557go-git: Malicious reference names may modify files outside the reference storage · 7 Aug 2026
- LowCVE-2026-45022Go-git: Improper parsing of specially crafted objects may lead to inconsistent interpretation in github.com/go-git/go-git · 24 Jul 2026
- LowCVE-2026-41506Go-git: Credential leak via cross-host redirect in smart HTTP transport in github.com/go-git/go-git · 24 Jul 2026
- LowCVE-2026-45571Go-git: Crafted repositories may modify main and submodule .git directories in github.com/go-git/go-git · 24 Jul 2026
- LowGO-2026-5693Go-git: Malformed Git object data may cause panics or resource exhaustion in github.com/go-git/go-git · 24 Jul 2026
References
- Linkgithub.com/go-git/go-git/security/advisories/GHSA-hc8v-wwc9-vgxm
- Linkgithub.com/go-git/go-git/commit/008a78f2dd86f52544ddff8b8e8ddeecdf3f7aab
- Linkgithub.com/go-git/go-git/commit/661d1c7f101d34e002a3cfcf8dbea5b7421d07ac
- Packagegithub.com/go-git/go-git
- Linkgithub.com/go-git/go-git/releases/tag/v5.19.2
- Linkgithub.com/go-git/go-git/releases/tag/v6.0.0-alpha.5
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.