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

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L`)
- **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:** Yes
- **Published:** 15 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-wqcr-7rf3-f64m, GO-2026-5715, UBUNTU-CVE-2026-47215

## 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 (Improper Limitation of a Pathname to a Restricted Directory)

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

## Is CVE-2026-47215 being exploited?

There is no known exploitation of CVE-2026-47215 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47215 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-47215 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/sylabs/singularity (Go): affected all versions; no fix listed
- github.com/sylabs/singularity (Go): affected all versions up to 3.1.1; no fix listed
- github.com/sylabs/singularity (Go): affected all versions up to 3.1.1; no fix listed
- github.com/sylabs/singularity/v4 (Go): affected all versions; fixed in 4.4.2
- github.com/sylabs/singularity/v4 (Go): affected all versions; fixed in 4.4.2
- github.com/sylabs/singularity/v4 (Go): affected all versions; fixed in 4.4.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47215/ (Markdown: https://insights.sbomify.com/CVE-2026-47215/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47215
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47215
- OSV: https://osv.dev/vulnerability/CVE-2026-47215

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47215/
Summaries are generated and may contain mistakes; the official description above is the record.