github.com/sylabs/singularity/v4
Affected
- introduced
0, fixed4.4.2(semver)
Fixed versions
4.4.2
Fix
- Fixed version
4.4.2go get github.com/sylabs/singularity/[email protected]
Advisory
Also known as: CVE-2026-47215, GO-2026-5715
Singluarity: Incorrect path matching for 'limit container paths' directive
Impact
The limit container paths directive in singularity.conf is intended to allow a system administrator limit the paths from which containers can be run, under setuid mode. Due to incorrect matching of a path string, sibling directories with similar names may incorrectly be allowed.
For example, the configuration:
limit container paths = /data/safe
Will also allow containers in /data/safe-but-unsafe to be run.
Patches
This issue is patched in SingularityCE 4.4.2 and SingularityPRO 4.3.9 / 4.1.14
Workarounds
If you do not use the limit container paths functionality, then this issue does not affect your installation.
If you do use the limit container paths functionality then you must update. Please also review the documented limitations when user namespaces are enabled [1].
Medium Basis: The source's own band: MODERATE
0, fixed 4.4.2 (semver)4.4.2
4.4.2go get github.com/sylabs/singularity/[email protected]0, last affected 3.1.1 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0