Loading…
How AI contributed
Incomplete remediationA symlink traversal issue in go-git could allow worktree operations to modify files outside the intended worktree path.
The highlighted steps are this advisory: the incomplete AI patch and the later commit that closed it.
This advisoryCVE-2026-71556 (GHSA-HC8V-WWC9-VGXM)
AI tried to fix this
The AI change was a real security patch, but it left the same advisory reachable.
Missed: validPath did not reject an existing leading symlink.
Fixed again
This is the patch that actually stops the same attack path.
Code comparison
go-git/go-git
Go- if err := sfs.validPath(filename); err != nil {+ if err := sfs.validWritePath(filename); err != nil {Every write now calls validWritePath instead of checking only the path string.
+func (sfs *worktreeFilesystem) validWritePath(paths ...string) error {+ if err := sfs.validPath(paths...); err != nil {+ return err+ }+ return sfs.validNoLeadingSymlink(paths...)+}The new write guard keeps string validation and adds an on-disk leading-symlink check.
Candidate 7aacf95dfbb036eb99a413847ef8a2cff24dc19cf58c392558b78d50b901bf8f · Fix e0f8f0751c4f5e14029dce536ed6b78eece0abc0da74f99ceced3ce71f5de68c
Releases
Advisory references