Detections
Analytics
CVE-2026-47215
medium
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.
References
https://github.com/sylabs/singularity/security/advisories/GHSA-wqcr-7rf3-f64m
https://github.com/sylabs/singularity/releases/tag/v4.4.2
https://github.com/sylabs/singularity/pull/4152
https://github.com/sylabs/singularity/commit/c1dc9470a769e6e534b588a4ed521768ca4fc0d1
https://github.com/sylabs/singularity/commit/c08791793e843d4c9c1f2fc1d9d12abef747378f