CVE-2026-47215: Singluarity: Incorrect path matching for 'limit container paths' directive ### Impact The `limit container paths` directive in `singularity.conf` is intended…

medium

Singluarity: Incorrect path matching for 'limit container paths' directive

### Impact

The `limit container paths` directive in `singularity.conf` is intended to allow a system administrator limit the paths from which containers can be run, under setuid mode. Due to incorrect matching of a path string, sibling directories with similar names may incorrectly be allowed.

For example, the configuration:

```
limit container paths = /data/safe
```

Will also allow containers in `/data/safe-but-unsafe` to be run.


### Patches

This issue is patched in SingularityCE 4.4.2 and SingularityPRO 4.3.9 / 4.1.14

### Workarounds

If you do not use the `limit container paths` functionality, then this issue does not affect your installation.

If you do use the `limit container paths` functionality then you must update. Please also review the documented limitations when user namespaces are enabled [1].

Affected

2 ranges

Vendor	Product	Version range	Fixed in
github.com	sylabs_singularity	0 – 3.1.1	—
github.com	sylabs_singularity_v4	>= 0 < 4.4.2	4.4.2

Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.