CVE-2026-47215: medium-severity vulnerability in sylabs singularity
Singularity: Incorrect path matching for 'limit container paths' directive
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 4.8epss 0.2%
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:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L
Related CVEs — sylabs singularity
In the same product, most dangerous first.
References
https://github.com/sylabs/singularity/commit/c08791793e843d4c9c1f2fc1d9d12abef747378fhttps://github.com/sylabs/singularity/commit/c1dc9470a769e6e534b588a4ed521768ca4fc0d1https://github.com/sylabs/singularity/pull/4152https://github.com/sylabs/singularity/releases/tag/v4.4.2https://github.com/sylabs/singularity/security/advisories/GHSA-wqcr-7rf3-f64m