CVE-2026-47215

MEDIUMPre-NVD 4.84.8—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 96% 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
4.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 4.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
4.8
EG Score
4.8MEDIUMmedium confidence
EG Risk
22
EG Risk 22/100

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 computed
Severity48% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

Published

June 4, 2026

Last Modified

September 25, 2026

Advisory Details (5)

Auto-updated Sep 15, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

SingularityCE 4.4.2

Patch available: sylabs/singularity v4.4.2

https://github.com/sylabs/singularity/releases/tag/v4.4.2
github_commit

commit c1dc9470a769 (sylabs/singularity)

Fix landed in sylabs/singularity commit c1dc9470a769 — awaiting tagged release

https://github.com/sylabs/singularity/commit/c1dc9470a769e6e534b588a4ed521768ca4fc0d1
github_commit

commit c08791793e84 (sylabs/singularity)

Fix landed in sylabs/singularity commit c08791793e84 — awaiting tagged release

https://github.com/sylabs/singularity/commit/c08791793e843d4c9c1f2fc1d9d12abef747378f
github_pr

Pick 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/4152
githubMentions a patch (unverified)

Incorrect path matching for 'limit container paths' directive · Advisory · sylabs/singularity · GitHub

https://github.com/sylabs/singularity/security/advisories/GHSA-wqcr-7rf3-f64m

Vendor 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)
PackageVulnerable rangeFix by version rangeDependents
github.com/sylabs/singularity—
  • every version through 3.1.1: no fix on record
  • every version on: no fix on record
—
github.com/sylabs/singularity/v4—
  • every version up to 4.4.2: fixed in 4.4.2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 21× 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.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:25 UTCEPSS rescore
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-09-30 15:03 UTCEPSS rescore
  10. 2026-09-28 13:51 UTCEPSS rescore
  11. 2026-09-27 13:48 UTCEPSS rescore
  12. 2026-09-26 15:59 UTCEPSS rescore
  13. 2026-09-26 00:27 UTCEPSS rescore
  14. 2026-09-25 14:42 UTCEG score recompute
  15. 2026-09-23 17:53 UTCEPSS rescore
  16. 2026-09-20 20:16 UTCEPSS rescore
  17. 2026-09-18 19:28 UTCEPSS rescore
  18. 2026-09-16 14:08 UTCEPSS rescore
  19. 2026-09-15 19:41 UTCEG score recompute
  20. 2026-09-15 18:25 UTCEG score recompute
  21. 2026-09-15 16:36 UTCEG score recompute
  22. 2026-07-31 05:26 UTCEG score recompute
  23. 2026-07-26 22:16 UTCEG score recompute
  24. 2026-07-23 03:17 UTCEG score recompute
  25. 2026-06-14 23:18 UTCEPSS rescore
Show 3 more
  1. 2026-06-13 23:00 UTCEPSS rescore
  2. 2026-06-12 23:12 UTCEPSS rescore
  3. 2026-06-04 18:10 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-47215?
CVE-2026-47215 is a medium vulnerability published on June 4, 2026. 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…
When was CVE-2026-47215 disclosed?
CVE-2026-47215 was first published on June 4, 2026, with the most recent update on September 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47215 actively exploited?
CVE-2026-47215 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47215?
CVE-2026-47215 has a CVSS base score of 4.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-47215?
A fix for CVE-2026-47215 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-47215 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47215

Explore →

Is Your Infrastructure Affected by CVE-2026-47215?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs