Vulnerability advisory
CVE-2026-52811
Gogs: UploadRepoFiles writes outside repo working tree via committed parent sym
Also known as GHSA-89mr-xqfv-758mGO-2026-5249
- CVSS 4.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Affected versions
Repository
| Affected commits | Fixed by commit |
|---|---|
| GIT github.com/gogs/gogs ↗ | |
| All commits before 3ba8aca90e17e5410b7e8b227c9f29256ac3e875 | 3ba8aca90e17e5410b7e8b227c9f29256ac3e875 |
| Not specified | 04cb8afbb01d855454e59977a1cdbf522ea1db31 |
Also listed as affected (59)
| |
Description
Gogs is an open source self-hosted Git service. Prior to 0.14.3, (*Repository).UploadRepoFiles checks for symlinks only on the leaf of the upload target (osx.IsSymlink(targetPath)). The siblings UpdateRepoFile, DeleteRepoFile, and GetDiffPreview use hasSymlinkInPath, which lstats every component — UploadRepoFiles is the lone outlier. An attacker with repo-write access plus a multipart upload whose filename contains a literal backslash (preserved by filepath.Base on Linux, then converted to / by pathx.Clean) redirects the write through a previously-committed directory symlink. iox.CopyFile opens the destination with os.Create (no O_NOFOLLOW), so the kernel follows the parent symlink and writes attacker bytes anywhere the gogs UID can write — ~git/.ssh/authorized_keys → SSH foothold, or <repo>.git/hooks/post-receive → next-push RCE. This vulnerability is fixed in 0.14.3.
References
- Webgithub.com/gogs/gogs/releases/tag/v0.14.3 ↗
- Advisorygithub.com/CVEProject/cvelistV5/tree/main/cves/2026/52xxx/CVE-2026-52811.json ↗
- Advisorygithub.com/gogs/gogs/security/advisories/GHSA-89mr-xqfv-758m ↗
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-52811 ↗
- Fixgithub.com/gogs/gogs/commit/04cb8afbb01d855454e59977a1cdbf522ea1db31 ↗
- Fixgithub.com/gogs/gogs/pull/8332 ↗