Answer in brief
CVE-2026-47215 records a Medium severity vulnerability in Singularity: Incorrect path matching for 'limit container paths' directive. The current sources do not mark it as known exploited. The current feed maps sylabs/singularity (generic), sylabs/SingularityPRO (generic), github.com/sylabs/singularity (go), github.com/sylabs/singularity/v4 (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps sylabs/singularity (generic), sylabs/SingularityPRO (generic), github.com/sylabs/singularity (go), github.com/sylabs/singularity/v4 (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| sylabs/singularitygeneric | < 4.4.2 | Not reported |
| sylabs/SingularityPROgeneric | < 4.1.14 || >= 4.2.0, < 4.3.9 | Not reported |
| github.com/sylabs/singularitygo | <=3.1.1 | Not reported |
| github.com/sylabs/singularity/v4go | <4.4.2 | 4.4.2 |
Published upstream
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 11, 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 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.
Quoted source text, attributed separately from HOL analysis.