The issue is related to the incorrect use of a default URL in Singularity, causing `singularity` action commands (`run`/`shell`/`exec`) to retrieve containers from the default remote endpoint (`cloud.sylabs.io`) instead of the configured remote endpoint when using a `library://` URI. This could allow an attacker to push a malicious container to the default remote endpoint, potentially executing it on a victim's system. Only action commands against `library://` URIs are affected, while other commands like `pull` and `push` respect the configured remote endpoint.