Vulnerability Description
SingularityCE and SingularityPRO are open source container platforms. Prior to SingularityCE 4.4.2 and SingularityPRO 4.3.9 and 4.1.14, incorrect path-string matching in the singularity.conf limit container paths directive allows a container in a sibling directory such as /data/safe-but-unsafe to be run when /data/safe is allowed under setuid mode. This permits a user to run a container from outside the administrator's configured path allowlist. Installations that do not use limit container paths are not affected. This issue is fixed in SingularityCE 4.4.2 and SingularityPRO 4.3.9 and 4.1.14.
CVSS Score
MEDIUM
Related Weaknesses (CWE)
References
- https://github.com/sylabs/singularity/commit/c08791793e843d4c9c1f2fc1d9d12abef74
- https://github.com/sylabs/singularity/commit/c1dc9470a769e6e534b588a4ed521768ca4
- https://github.com/sylabs/singularity/pull/4152
- https://github.com/sylabs/singularity/releases/tag/v4.4.2
- https://github.com/sylabs/singularity/security/advisories/GHSA-wqcr-7rf3-f64m
FAQ
What is CVE-2026-47215?
CVE-2026-47215 is a vulnerability with a CVSS score of 4.8 (MEDIUM). SingularityCE and SingularityPRO are open source container platforms. Prior to SingularityCE 4.4.2 and SingularityPRO 4.3.9 and 4.1.14, incorrect path-string matching in the singularity.conf limit con...
How severe is CVE-2026-47215?
CVE-2026-47215 has been rated MEDIUM with a CVSS base score of 4.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-47215?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.