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…

PriorityP422medium4.8CVSS 3.1

AVLACLPRLUIRSUCLILAL

EPSS

0.15%

4.3th percentile

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

5 ranges

Vendor	Product	Version range	Fixed in
github.com	sylabs_singularity	0 – 3.1.1	—
github.com	sylabs_singularity_v4	>= 0 < 4.4.2	4.4.2
sylabs	singularity	< 4.4.2	4.4.2
sylabs	singularitypro	< 4.1.14	4.1.14
sylabs	singularitypro	—	—

Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.