Skip to content

CVE-2026-47215 Singularity: Incorrect path matching for 'limit container paths' directive

MediumCVSS 4.8 EPSS 0.16%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
No known exploitation · automatable: no · technical impact: partial
Technology
Ubuntu

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.

Upgrade path

6 packages: 1 fixed, 1 partially fixed, 2 with no fix yet.

PackageAffectedFixed inStatus
ubuntu/singularity-container(Ubuntu 24.04) All versions No fix listed No fix yet
ubuntu/singularity-container(Ubuntu 26.04) All versions No fix listed No fix yet
sylabs github.com/sylabs/singularity(Go) < 4.4.2; <= 3.1.1; All versions 4.4.2 Partially fixed
alpine/singularity(Alpine v3.24) < 4.4.2-r0 4.4.2-r0 Fixed
sylabs github.com/sylabs/singularity = < 4.4.2 No fix listed Versions listed
sylabs SingularityPRO = < 4.1.14; = >= 4.2.0, < 4.3.9 No fix listed Versions listed

Affected products

ProductAffected versionsFixed in
sylabs github.com/sylabs/singularity = < 4.4.2 No fix listed
sylabs SingularityPRO = < 4.1.14 No fix listed
sylabs SingularityPRO = >= 4.2.0, < 4.3.9 No fix listed
sylabs github.com/sylabs/singularity(Go) < 4.4.2 4.4.2
sylabs github.com/sylabs/singularity(Go) <= 3.1.1 No fix listed
sylabs github.com/sylabs/singularity(Go) All versions No fix listed
alpine/singularity(Alpine:v3.24) < 4.4.2-r0 4.4.2-r0
ubuntu/singularity-container(Ubuntu:24.04) All versions No fix listed
ubuntu/singularity-container(Ubuntu:26.04) All versions No fix listed

References