CVE-2026-47215 json
Singularity: Incorrect path matching for 'limit container paths' directive
published 2026-06-04 5 mo ago modified 2026-09-25 45 d ago also EUVD-2026-78779 , GHSA-wqcr-7rf3-f64m , GO-2026-5715
- cvss
- 4.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 4%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/sylabs/singularity/v4 4.4.2
- sylabs singularity 4.4.2
- sylabs singularitypro 4.1.14, 4.3.9
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
opensuse advisories openSUSE-SU-2026:21483-1
- singularity Alpine 3.24 4.4.2-r0
alpine advisories ALPINE-CVE-2026-47215
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 54 d ago
Exploit prediction
0.15% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L |
| GitHub | 3.1 | 4.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/sylabs/singularity/v4 | <4.4.2 |
4.4.2 |
| go | github.com/sylabs/singularity | <=3.1.1 all versions |
no fix listed |
Affected products
- sylabs singularity
- sylabs SingularityPRO
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
- github.com /sylabs/singularity/pull/4152
-
github.com
/sylabs/singularity/commit/c08791793e843d4c9c1f2fc1d9d12abef747378f
web, patch
- github.com /sylabs/singularity/commit/c1dc9470a769e6e534b588a4ed521768ca4fc0d1
-
github.com
/sylabs/singularity/security/advisories/GHSA-wqcr-7rf3-f64m
web, advisory
-
github.com
/sylabs/singularity/releases/tag/v4.4.2
web
-
docs.sylabs.io
/guides/latest/admin-guide/configfiles.html#limiting-container-execution
web
-
github.com
/sylabs/singularity
package
Sources
- CVE List CVE-2026-47215
- GitHub Advisory GHSA-wqcr-7rf3-f64m
- NVD CVE-2026-47215
- OSV GO-2026-5715
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.