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.
CVE-2026-47215
This medium-severity CVE scores 4.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.0%, top 99% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.8
- EG Score
- 4.8(low)
- EG Risk
- 22(Track)EG Risk 22/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity48% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 4%
- KEV
- Not listed
Published
June 4, 2026
Last Modified
September 15, 2026
Advisory Details (5)
Auto-updated Sep 15, 2026SingularityCE 4.4.2
Patch available: sylabs/singularity v4.4.2
https://github.com/sylabs/singularity/releases/tag/v4.4.2commit c1dc9470a769 (sylabs/singularity)
Fix landed in sylabs/singularity commit c1dc9470a769 — awaiting tagged release
https://github.com/sylabs/singularity/commit/c1dc9470a769e6e534b588a4ed521768ca4fc0d1commit c08791793e84 (sylabs/singularity)
Fix landed in sylabs/singularity commit c08791793e84 — awaiting tagged release
https://github.com/sylabs/singularity/commit/c08791793e843d4c9c1f2fc1d9d12abef747378fPick limit container paths fix and prepare 4.4.2 release
Fix merged in sylabs/singularity PR #4152 on 2026-06-04 — awaiting tagged release
https://github.com/sylabs/singularity/pull/4152Incorrect path matching for 'limit container paths' directive · Advisory · sylabs/singularity · GitHub
https://github.com/sylabs/singularity/security/advisories/GHSA-wqcr-7rf3-f64mVendor Advisories for CVE-2026-47215(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(2 across 1 ecosystem)
Go(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/sylabs/singularity | — | — | — |
| github.com/sylabs/singularity/v4 | — | 4.4.2 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-15 19:41 UTCEG score recompute
- 2026-09-15 18:25 UTCEG score recompute
- 2026-09-15 16:36 UTCEG score recompute
- 2026-07-31 05:26 UTCEG score recompute
- 2026-07-26 22:16 UTCEG score recompute
- 2026-07-23 03:17 UTCEG score recompute
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-04 18:10 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-47215?
When was CVE-2026-47215 disclosed?
Is CVE-2026-47215 actively exploited?
What is the CVSS score of CVE-2026-47215?
How do I remediate CVE-2026-47215?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47215
Is Your Infrastructure Affected by CVE-2026-47215?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.