GHSA-jq42-hfch-42f3 — singularity
MEDIUMGHSA-jq42-hfch-42f3 is a medium-severity (CVSS 6.3) vulnerability in github.com/hpcng/singularity. A fix is available for github.com/hpcng/singularity — see the affected versions and patch details below.
Action Commands (run/shell/exec) Against Library URIs Ignore Configured Remote Endpoint
Real-World Exposure
github.com/hpcng/singularityReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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 issue was found by Mike Frisch and brought to our attention by Sylabs. Sylabs is making a coordinated disclosure.
For more information
General questions about the impact of the advisory can be asked in the:
Singularity Slack Channel Singularity Mailing List Any sensitive security concerns should be directed to: [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/hpcng/singularity | ≥ 3.7.2&&< 3.7.4 | 3.7.4go get github.com/hpcng/singularity@v3.7.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/hpcng/singularity, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/hpcng/singularity to 3.7.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jq42-hfch-42f3 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-jq42-hfch-42f3 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-jq42-hfch-42f3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-jq42-hfch-42f3 in your dependencies?
O3 Security finds GHSA-jq42-hfch-42f3 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.