Skip to content
OpenAdvisories
Medium · 4.8 CVE-2026-47215 EUVD-2026-78779GHSA-wqcr-7rf3-f64mGO-2026-5715

Singularity: Incorrect path matching for 'limit container paths' directive

Published Sep 15, 2026 · Updated Sep 15, 2026 · Assigned by GitHub_M

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.

Affected products

VendorProductAffectedFixed
sylabs singularity < 4.4.2 —
sylabs SingularityPRO < 4.1.14, >= 4.2.0, < 4.3.9 —

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
Ubuntu 26.04 LTS singularity-container No fix yet —
Ubuntu 25.10 singularity-container No fix yet —
Show 2 more (older releases, extended support, other products)
ReleasePackageFixed inAdvisory
Ubuntu Pro 24.04 LTS singularity-container No fix yet —
Ubuntu Pro 18.04 LTS singularity-container No fix yet —
ReleasePackageFixed inAdvisory
openSUSE Leap 16.0 govulncheck-vulndb 0.0.20260723T184607-160000.1.1 openSUSE-SU-2026:21483-1
ReleasePackageFixed inAdvisory
Alpine v3.24 singularity 4.4.2-r0 —

Affected packages

EcosystemPackageAffectedFixedRecord
Go github.com/sylabs/singularity <= 3.1.1 — GHSA-wqcr-7rf3-f64m
Go github.com/sylabs/singularity all versions — GO-2026-5715
Go github.com/sylabs/singularity/v4 < 4.4.2 4.4.2 GHSA-wqcr-7rf3-f64m

Advisories 1

References