---
id: CVE-2026-47215
title: SingularityCE and SingularityPRO are open source container platforms
summary: >-
  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
  conta…
severity: medium
cvss: 4.8
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L'
cwe:
  - CWE-22
vendor: sylabs
product: singularity
affected:
  - singularity < 4.4.2
  - SingularityPRO < 4.1.14
  - 'SingularityPRO >= 4.2.0, < 4.3.9'
published: '2026-09-15'
updated: '2026-09-25'
sourceUpdated: '2026-09-25T14:23:59.847'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-47215'
references:
  - url: >-
      https://github.com/sylabs/singularity/commit/c08791793e843d4c9c1f2fc1d9d12abef747378f
    label: security-advisories@github.com
  - url: >-
      https://github.com/sylabs/singularity/commit/c1dc9470a769e6e534b588a4ed521768ca4fc0d1
    label: security-advisories@github.com
  - url: 'https://github.com/sylabs/singularity/pull/4152'
    label: security-advisories@github.com
  - url: 'https://github.com/sylabs/singularity/releases/tag/v4.4.2'
    label: security-advisories@github.com
  - url: >-
      https://github.com/sylabs/singularity/security/advisories/GHSA-wqcr-7rf3-f64m
    label: security-advisories@github.com
tags:
  - nvd
  - cve.org
epss: 0.00155
epssPercentile: 0.0389
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-09-15T17:38:21.591354Z'
ingestedAt: '2026-09-15T15:39:12.932Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.