UNIX Symbolic Link (Symlink) Following Affecting github.com/moby/moby/v2 package, versions <2.0.0-beta.14
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-GOLANG-GITHUBCOMMOBYMOBYV2-16755305
- published19 May 2026
- disclosed18 May 2026
- creditAsim Viladi Oglu Manizada
Introduced: 18 May 2026
CVE-2026-41568 Â (opens in a new tab)How to fix?
Upgrade github.com/moby/moby/v2 to version 2.0.0-beta.14 or higher.
Overview
Affected versions of this package are vulnerable to UNIX Symbolic Link (Symlink) Following during docker cp mount setup due to the switching from GetResourcePath and to createIfNotExists method that has no absolute path checks. An attacker can create empty files or directories at arbitrary absolute paths on the host filesystem by rapidly swapping symlinks at a volume mount destination path during the mount setup phase. This is only exploitable if a container is running with a process that can rapidly create and swap symlinks at a volume mount destination path and an operator initiates a file copy into that container or calls the relevant archive API endpoints.
Workaround
This vulnerability can be mitigated by only running containers from trusted images, avoiding the use of file copy operations with untrusted running containers, and using authorization plugins to restrict access to the archive API endpoints.