Most recent entries from all

fkie_cve-2026-47215

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.

GHSA-wqcr-7rf3-f64m — Singluarity: Incorrect path matching for 'limit container paths' directive

Affected: Go: github.com/sylabs/singularity/v4, Go: github.com/sylabs/singularity

### 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].

UBUNTU-CVE-2026-47215

Affected: Ubuntu:Pro:18.04:LTS: singularity-container, Ubuntu:Pro:24.04:LTS: singularity-container, Ubuntu:25.10: singularity-container, Ubuntu:26.04:LTS: singularity-container