Is CVE-2026-47215 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-47215 being exploited in the wild.

How severe is CVE-2026-47215?

Medium severity, with a CVSS score of 4.8, published 15 September 2026.

Which products and versions are affected?

github.com/sylabs/singularity (Go) <= 3.1.1, SEMVER:introduced=0, SEMVER:introduced=0,last_affected=3.1.1; github.com/sylabs/singularity/v4 (Go) < 4.4.2, SEMVER:introduced=0,fixed=4.4.2; Sylabs SingularityCE < 4.4.2, <= 3.1.1; Sylabs SingularityPRO < 4.3.9, < 4.1.14.

Is there a fix for CVE-2026-47215?

Yes. github.com/sylabs/singularity/v4 (Go): upgrade to 4.4.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-47215 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-47215?

Check whether you run github.com/sylabs/singularity (Go), github.com/sylabs/singularity/v4 (Go), Sylabs SingularityCE or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-47215: Sylabs Singularity incorrect path matching in limit container paths

Q: Is there a fix for CVE-2026-47215?

Yes. github.com/sylabs/singularity/v4 (Go): upgrade to 4.4.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-47215 attacked?

It is attacked with local access, in a software library.

Q: Am I affected by CVE-2026-47215?

Check whether you run github.com/sylabs/singularity (Go), github.com/sylabs/singularity/v4 (Go), Sylabs SingularityCE or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-47215 · Severity: medium · CVSS 4.8 · Published 2026-09-15

Singularity is a container platform often used in high-performance computing environments. A security flaw in its configuration handling allows users to run containers from unauthorized directories if those directories have names that start with the same characters as an authorized path. This bypasses administrative restrictions intended to ensure only trusted software is executed in sensitive environments.

Technologies: github.com/sylabs/singularity (Go). Vendors: Go.

Quick answers

Is CVE-2026-47215 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-47215 being exploited in the wild.
How severe is CVE-2026-47215?: Medium severity, with a CVSS score of 4.8, published 15 September 2026.
Which products and versions are affected?: github.com/sylabs/singularity (Go) <= 3.1.1, SEMVER:introduced=0, SEMVER:introduced=0,last_affected=3.1.1; github.com/sylabs/singularity/v4 (Go) < 4.4.2, SEMVER:introduced=0,fixed=4.4.2; Sylabs SingularityCE < 4.4.2, <= 3.1.1; Sylabs SingularityPRO < 4.3.9, < 4.1.14.
Is there a fix for CVE-2026-47215?: Yes. github.com/sylabs/singularity/v4 (Go): upgrade to 4.4.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-47215 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-47215?: Check whether you run github.com/sylabs/singularity (Go), github.com/sylabs/singularity/v4 (Go), Sylabs SingularityCE or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/sylabs/singularity/v4 (Go): upgrade to 4.4.2 or later
```
go get github.com/sylabs/singularity/v4@v4.4.2
```

Technical details

A path traversal/incorrect matching vulnerability (CWE-22) exists in Singularity's 'limit container paths' directive within singularity.conf. When operating in setuid mode, the runtime performs string-based prefix matching rather than strict directory boundary matching. An attacker with local access can bypass execution restrictions by placing container images in sibling directories that share a prefix with an allowed path (e.g., '/data/safe-unauthorized' matching a rule for '/data/safe'). This allows for the execution of unauthorized containers in environments where path-based restrictions are enforced. The issue is resolved in SingularityCE 4.4.2 and SingularityPRO 4.3.9 / 4.1.14.

Affected products

Sylabs SingularityCE < 4.4.2, <= 3.1.1
Sylabs SingularityPRO < 4.3.9, < 4.1.14

Identifiers

CVE-2026-47215
GHSA-wqcr-7rf3-f64m
GO-2026-5715

Timeline

2026-06-04: disclosed
2026-06-04: advisory
2026-06-04: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.