CVE-2026-47215
MediumCVSS 4.8Exploitation Probability (EPSS)
Low risk4th percentile - higher than 4% of all known CVEs
Summary
In SingularityCE and SingularityPRO prior to 4.4.2 and 4.3.9/4.1.14 respectively, 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.
Risk Assessment
A user can bypass administrative path restrictions and run containers from disallowed locations, violating the organization's security policy.
Recommendation
Upgrade SingularityCE to 4.4.2 or later and SingularityPRO to 4.3.9 or 4.1.14 (or later).
Other vulnerabilities in SingularityCE
Original NVD description (English source)
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.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS

