Action Commands (run/shell/exec) Against Library URIs Ignore Configured Remote Endpoint

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact Due to incorrect use of a default URL, singularity action commands (run/shell/exec) specifying a container using a library:// URI will always attempt to retrieve the container from the default remote endpoint (cloud.sylabs.io) rather than the configured remote endpoint. An attacker may be able to push a malicious container to the default remote endpoint with a URI that is identical to the URI used by a victim with a non-default remote endpoint, thus executing the malicious container. Only action commands (run/shell/exec) against library:// URIs are affected. Other commands such as pull / push respect the configured remote endpoint. Patches All users should upgrade to Singularity 3.7.4 or later. Workarounds Users who only interact with the default remote endpoint or do not use the library:// url are not affected. Installations with an execution control list configured to restrict execution to containers signed with specific secure keys are not affected. Acknowledgements This…

Published by the source

1 Jun 2021, 21:20 UTC

Last modified by the source

9 Jan 2023, 05:04 UTC

Source last checked

26 Oct 2026, 14:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-jq42-hfch-42f3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-jq42-hfch-42f3

Advisory: Action Commands (run/shell/exec) Against Library URIs Ignore Configured Remote Endpoint
IDs: GHSA-jq42-hfch-42f3
Record: https://patchnext.com/advisories/ghsa-jq42-hfch-42f3 (revision 1, source checked 26 Oct 2026, 14:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/hpcng/singularity 3.7.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/hpcng/singularity: affected >= 3.7.2, < 3.7.4; fixed in 3.7.4

## Suggested inspection (read-only)
- Go github.com/hpcng/singularity: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/hpcng/singularity.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-jq42-hfch-42f3 (GitHub-reviewed advisory GHSA-jq42-hfch-42f3 lists affected ranges: Go github.com/hpcng/singularity >=3.7.2 <3.7.4)

Commands are suggestions: review each one before running it.