CVE-2026-47215
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.
How to fix
- github.com/sylabs/singularity/v44.4.2 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| github.com/sylabs/singularity/v4Go | v < 4.4.2 | 4.4.2 |
| github.com/sylabs/singularityGo | v ≤ 3.1.1, No range specified | — |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.