CVE-2026-47215

MEDIUMPre-NVD 4.84.8
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 4.8 under the CNA's CVSS (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).

Triggered by: NVD CVSS baseline
Sources: cna:github_m, epss
4.8
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Singluarity: Incorrect path matching for 'limit container paths' directive

Impact

The limit container paths directive in singularity.conf is intended to allow a system administrator limit the paths from which containers can be run, under setuid mode. Due to incorrect matching of a path string, sibling directories with similar names may incorrectly be allowed.

For example, the configuration:

limit container paths = /data/safe

Will also allow containers in /data/safe-but-unsafe to be run.

Patches

This issue is patched in SingularityCE 4.4.2 and SingularityPRO 4.3.9 / 4.1.14

Workarounds

If you do not use the limit container paths functionality, then this issue does not affect your installation.

If you do use the limit container paths functionality then you must update. Please also review the documented limitations when user namespaces are enabled [1].

CVSS v3
4.8
EG Score
4.8(low)
EPSS
1.1%
KEV
Not listed

Published

June 4, 2026

Last Modified

June 4, 2026

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 rangeFixed inDependents
github.com/sylabs/singularity———
github.com/sylabs/singularity/v4—4.4.2—

Data Freshness Timeline

(refreshed 4× in last 7d / 28× 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-07-11 11:56 UTCEG score recompute
  2. 2026-07-09 07:46 UTCEG score recompute
  3. 2026-07-08 09:38 UTCEG score recompute
  4. 2026-07-06 02:50 UTCEG score recompute
  5. 2026-07-03 19:15 UTCEG score recompute
  6. 2026-07-02 16:59 UTCEG score recompute
  7. 2026-07-01 18:46 UTCEG score recompute
  8. 2026-06-30 20:04 UTCEG score recompute
  9. 2026-06-29 13:56 UTCEG score recompute
  10. 2026-06-28 15:50 UTCEG score recompute
  11. 2026-06-27 17:38 UTCEG score recompute
  12. 2026-06-26 19:26 UTCEG score recompute
  13. 2026-06-25 21:20 UTCEG score recompute
  14. 2026-06-24 23:14 UTCEG score recompute
  15. 2026-06-24 01:08 UTCEG score recompute
  16. 2026-06-23 01:55 UTCEG score recompute
  17. 2026-06-19 19:48 UTCEG score recompute
  18. 2026-06-18 16:21 UTCEG score recompute
  19. 2026-06-17 17:24 UTCEG score recompute
  20. 2026-06-16 18:07 UTCEG score recompute
  21. 2026-06-15 19:57 UTCEG score recompute
  22. 2026-06-14 23:18 UTCEPSS rescore
  23. 2026-06-14 21:14 UTCEG score recompute
  24. 2026-06-13 23:08 UTCEG score recompute
  25. 2026-06-13 23:00 UTCEPSS rescore
Show 11 more
  1. 2026-06-13 01:02 UTCEG score recompute
  2. 2026-06-12 23:12 UTCEPSS rescore
  3. 2026-06-12 02:56 UTCEG score recompute
  4. 2026-06-11 04:50 UTCEG score recompute
  5. 2026-06-10 06:44 UTCEG score recompute
  6. 2026-06-09 08:39 UTCEG score recompute
  7. 2026-06-08 10:33 UTCEG score recompute
  8. 2026-06-07 12:27 UTCEG score recompute
  9. 2026-06-06 14:21 UTCEG score recompute
  10. 2026-06-05 16:16 UTCEG score recompute
  11. 2026-06-04 18:10 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-47215?
CVE-2026-47215 is a medium vulnerability published on June 4, 2026. Singluarity: Incorrect path matching for 'limit container paths' directive Impact The limit container paths directive in singularity.conf is intended to allow a system administrator limit the paths from which containers can be run, under setuid mode. Due to incorrect matching of a path string,…
When was CVE-2026-47215 disclosed?
CVE-2026-47215 was first published in the National Vulnerability Database on June 4, 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 1.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-47215?
CVE-2026-47215 has a CVSS v4.0 base score of 4.8 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-47215?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47215, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs