Incorrect Permission Assignment for Critical Resource in SingularityGHSA-557g-r22w-9wvx
HIGHFix: sylabs/singularity@618c9d5GHSA-557g-r22w-9wvx is a high-severity (CVSS 8.8) CWE-732 vulnerability in github.com/sylabs/singularity. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for github.com/sylabs/singularity — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/sylabs/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
An issue was discovered in Singularity 3.1.0 to 3.2.0-rc2, a malicious user with local/network access to the host system (e.g. ssh) could exploit this vulnerability due to insecure permissions allowing a user to edit files within /run/singularity/instances/sing/<user>/<instance>. The manipulation of those files can change the behavior of the starter-suid program when instances are joined resulting in potential privilege escalation on the host.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/sylabs/singularity | ≥ 3.1.0&&< 3.2.0 | 3.2.0go get github.com/sylabs/singularity@v3.2.0 |
Affected Products
fedorafedoraprojectbackportsopensuseleapopensusesingularitysylabsResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/sylabs/singularity, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/sylabs/singularity to 3.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-557g-r22w-9wvx is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Frequently Asked Questions
Is GHSA-557g-r22w-9wvx in your dependencies?
Find it across Go, including transitive dependencies.