CVE-2026-47215

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].

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.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2026-47215 has a CVSS score of 4.8 (Medium). The vector is requires local access, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.4.2); upgrading removes the vulnerable code path.

Kodem intelligence

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

1. What is CVE-2026-47215? CVE-2026-47215 is a medium-severity path traversal vulnerability in github.com/sylabs/singularity/v4 (go), affecting versions < 4.4.2. It is fixed in 4.4.2. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2026-47215? CVE-2026-47215 has a CVSS score of 4.8 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2026-47215?
   • github.com/sylabs/singularity/v4 (go) (versions < 4.4.2)
   • github.com/sylabs/singularity (go) (versions <= 3.1.1)
4. Is there a fix for CVE-2026-47215? Yes. CVE-2026-47215 is fixed in 4.4.2. Upgrade to this version or later.
5. Is CVE-2026-47215 exploitable, and should I be worried? Whether CVE-2026-47215 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-47215 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-47215? Upgrade github.com/sylabs/singularity/v4 to 4.4.2 or later.