CVE-2026-47215: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in sylabs singularity
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.
AI Analysis
Technical Summary
SingularityCE and SingularityPRO are open source container platforms by Sylabs. Before SingularityCE 4.4.2 and SingularityPRO 4.3.9 and 4.1.14, the limit container paths directive in singularity.conf had incorrect path-string matching. This flaw allowed a container located in a sibling directory (e.g., /data/safe-but-unsafe) to be run even when only /data/safe was allowed, effectively bypassing the administrator's configured path allowlist under setuid mode. This improper limitation of pathname to a restricted directory (CWE-22) could lead to unauthorized container execution from outside the intended directory restrictions. Systems not using the limit container paths directive are unaffected. The vulnerability has a CVSS 3.1 base score of 4.8, indicating medium severity. The issue is resolved in SingularityCE 4.4.2 and SingularityPRO 4.3.9 and 4.1.14.
Potential Impact
An attacker with limited privileges can bypass configured directory restrictions and run containers from unauthorized sibling directories under setuid mode. This could lead to unauthorized container execution with potential confidentiality, integrity, and availability impacts, though the overall severity is medium. Systems not using the limit container paths directive are not impacted.
Mitigation Recommendations
Upgrade SingularityCE to version 4.4.2 or later, or SingularityPRO to version 4.3.9 or 4.1.14 or later to apply the official fix. If the limit container paths directive is not used, the system is not affected and no action is required.
CVE-2026-47215: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in sylabs singularity
Description
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.1
Score 4.8medium
Affected software
sylabs
singularity
sylabs
SingularityPRO
pkg:github/sylabs/singularityRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
SingularityCE and SingularityPRO are open source container platforms by Sylabs. Before SingularityCE 4.4.2 and SingularityPRO 4.3.9 and 4.1.14, the limit container paths directive in singularity.conf had incorrect path-string matching. This flaw allowed a container located in a sibling directory (e.g., /data/safe-but-unsafe) to be run even when only /data/safe was allowed, effectively bypassing the administrator's configured path allowlist under setuid mode. This improper limitation of pathname to a restricted directory (CWE-22) could lead to unauthorized container execution from outside the intended directory restrictions. Systems not using the limit container paths directive are unaffected. The vulnerability has a CVSS 3.1 base score of 4.8, indicating medium severity. The issue is resolved in SingularityCE 4.4.2 and SingularityPRO 4.3.9 and 4.1.14.
Potential Impact
An attacker with limited privileges can bypass configured directory restrictions and run containers from unauthorized sibling directories under setuid mode. This could lead to unauthorized container execution with potential confidentiality, integrity, and availability impacts, though the overall severity is medium. Systems not using the limit container paths directive are not impacted.
Mitigation Recommendations
Upgrade SingularityCE to version 4.4.2 or later, or SingularityPRO to version 4.3.9 or 4.1.14 or later to apply the official fix. If the limit container paths directive is not used, the system is not affected and no action is required.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-18T22:25:21.258Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6aa9651655bf5e2cf502e92b
Added to database: 09/15/2026, 15:32:38 UTC
Last enriched: 09/15/2026, 16:17:18 UTC
Last updated: 09/15/2026, 22:11:30 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.