CVE-2026-47215 Singularity: Incorrect path matching for 'limit container paths' directive
Incorrect path matching in Singularity allows users to bypass container path restrictions and run unauthorized containers from sibling directories.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-47215?
CVE-2026-47215 is a medium-severity path traversal vulnerability in sylabs SingularityPRO, published on 15 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Official 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.
Weakness: CWE-22
Which versions are affected by CVE-2026-47215?
6 open source packages ship an affected version, including github.com/sylabs/singularity and github.com/sylabs/singularity/v4.
| Package | Affected | Fixed in |
|---|---|---|
github.com/sylabs/singularity Go | All versions | None |
github.com/sylabs/singularity Go | All versions to 3.1.1 | None |
github.com/sylabs/singularity Go | All versions to 3.1.1 | None |
github.com/sylabs/singularity/v4 Go | All versions | 4.4.2 |
github.com/sylabs/singularity/v4 Go | All versions | 4.4.2 |
github.com/sylabs/singularity/v4 Go | All versions | 4.4.2 |
How do I fix CVE-2026-47215?
Upgrade to a fixed version.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2026-47215 being exploited?
There is no known exploitation of CVE-2026-47215 in the wild and no public exploit code.
Sources
Also known as GHSA-wqcr-7rf3-f64m, GO-2026-5715, UBUNTU-CVE-2026-47215.