CVE-2026-47215 is a medium-severity (CVSS 4.8) vulnerability in github.com/sylabs/singularity/v4. O3 Security confirms whether CVE-2026-47215 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Singluarity: Incorrect path matching for 'limit container paths' directive
Real-World Exposure
github.com/sylabs/singularity/v4🐹github.com/sylabs/singularityReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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].
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/sylabs/singularity/v4 | all versions | 4.4.2 |
| 🐹Go | github.com/sylabs/singularity | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/sylabs/singularity/v4. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/sylabs/singularity/v4 to 4.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-47215 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-47215 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-47215. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-47215 in your dependencies?
O3 detects CVE-2026-47215 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.