The issue allows cache poisoning from other projects built on the same host, resulting in attacker-controlled code entering a server-side build process. This occurs because of the way that dist packages are cached, with the cache key derived from the package name, the dist type, and certain other data from the package repository, such as a commit hash that can be found by an attacker.