CVE-2026-47215
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
- Versión: 3.1
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L
- Puntuación base: 4.8
Probabilidad de explotación (EPSS)
- Probabilidad de explotación en los próximos 30 días: 0.15%
- Percentil entre todas las CVEs puntuadas: 4
- Fecha de la puntuación: 5/10/2026
EPSS (Exploit Prediction Scoring System, de FIRST) estima la probabilidad de que una vulnerabilidad sea explotada en 30 días. Complementa a CVSS (impacto) y a CISA KEV (explotación confirmada).
Tecnologías afectadas (2)
⚠ Inferidas por IA a partir de la descripción — NVD aún no ha analizado esta CVE; no son CPE verificados.
CWE
- CWE-22
Referencias
- https://github.com/sylabs/singularity/commit/c08791793e843d4c9c1f2fc1d9d12abef747378f
- https://github.com/sylabs/singularity/commit/c1dc9470a769e6e534b588a4ed521768ca4fc0d1
- https://github.com/sylabs/singularity/pull/4152
- https://github.com/sylabs/singularity/releases/tag/v4.4.2
- https://github.com/sylabs/singularity/security/advisories/GHSA-wqcr-7rf3-f64m
JSON original (NVD)
Mostrar
{
"id": "CVE-2026-47215",
"cveTags": [],
"metrics": {
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-47215",
"role": "CISA Coordinator",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"version": "2.0.3",
"timestamp": "2026-09-15T17:38:21.591354Z"
}
}
],
"cvssMetricV31": [
{
"type": "Secondary",
"source": "security-advisories@github.com",
"cvssData": {
"scope": "UNCHANGED",
"version": "3.1",
"baseScore": 4.8,
"attackVector": "LOCAL",
"baseSeverity": "MEDIUM",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L",
"integrityImpact": "LOW",
"userInteraction": "REQUIRED",
"attackComplexity": "LOW",
"availabilityImpact": "LOW",
"privilegesRequired": "LOW",
"confidentialityImpact": "LOW"
},
"impactScore": 3.4,
"exploitabilityScore": 1.3
}
]
},
"affected": [
{
"source": "security-advisories@github.com",
"affectedData": [
{
"vendor": "sylabs",
"product": "singularity",
"versions": [
{
"status": "affected",
"version": "< 4.4.2"
}
]
},
{
"vendor": "sylabs",
"product": "SingularityPRO",
"versions": [
{
"status": "affected",
"version": "< 4.1.14"
},
{
"status": "affected",
"version": ">= 4.2.0, < 4.3.9"
}
]
}
]
}
],
"published": "2026-09-15T16:17:11.170",
"references": [
{
"url": "https://github.com/sylabs/singularity/commit/c08791793e843d4c9c1f2fc1d9d12abef747378f",
"source": "security-advisories@github.com"
},
{
"url": "https://github.com/sylabs/singularity/commit/c1dc9470a769e6e534b588a4ed521768ca4fc0d1",
"source": "security-advisories@github.com"
},
{
"url": "https://github.com/sylabs/singularity/pull/4152",
"source": "security-advisories@github.com"
},
{
"url": "https://github.com/sylabs/singularity/releases/tag/v4.4.2",
"source": "security-advisories@github.com"
},
{
"url": "https://github.com/sylabs/singularity/security/advisories/GHSA-wqcr-7rf3-f64m",
"source": "security-advisories@github.com"
}
],
"vulnStatus": "Awaiting Analysis",
"weaknesses": [
{
"type": "Secondary",
"source": "security-advisories@github.com",
"description": [
{
"lang": "en",
"value": "CWE-22"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "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."
}
],
"lastModified": "2026-09-25T14:23:59.847",
"sourceIdentifier": "security-advisories@github.com"
}