CVE-2026-47215: Singluarity Incorrect Path Matching For 'limit Vulnerability
MODERATECVE-2026-47215 is a MODERATE (CVSS 4.8) incorrect path matching for 'limit vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting Singluarity libraries in the Go ecosystem. The issue involves incorrect path matching for 'limit container paths' directive. Remediation is available by upgrading affected packages to version 4.4.2.
CVE-2026-47215 at a Glance
Security Impact
CVSS: 4.8
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L).
How to Fix CVE-2026-47215
To remediate this vulnerability, upgrade all affected Singluarity dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/sylabs/singularity/v4 to 4.4.2Upgrade github.com/sylabs/singularity to Latest secure releaseRun the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/sylabs/singularity/v4How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-47215, inspect your project dependencies for Singluarity:
inspect dependencies for github.com/sylabs/singularity/v4Analyze the terminal output to locate any version of Singluarity in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.4.2), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where the product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. In Singluarity, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-47215 Affected Singluarity Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/sylabs/singularity/v4
|
Go |
< 4.4.2
|
4.4.2
|
|
github.com/sylabs/singularity
|
Go |
≤ 3.1.1
|
|
References
Frequently Asked Questions
What is CVE-2026-47215?
Which Singluarity versions are affected?
What version fixes CVE-2026-47215?
Is github.com/sylabs/singularity/v4 affected?
Is github.com/sylabs/singularity affected?
What is the CVSS score of CVE-2026-47215?
What CWE is associated with CVE-2026-47215?
How can I check Go dependencies for CVE-2026-47215?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-wqcr-7rf3-f64m",
"modified" : "2026-06-04T17:38:21Z",
"published" : "2026-06-04T17:38:21Z",
"aliases" : [ "CVE-2026-47215" ],
"summary" : "Singluarity: Incorrect path matching for 'limit container paths' directive",
"details" : "### Impact\n\nThe `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.\n\nFor example, the configuration:\n\n```\nlimit container paths = /data/safe\n```\n\nWill also allow containers in `/data/safe-but-unsafe` to be run.\n\n\n### Patches\n\nThis issue is patched in SingularityCE 4.4.2 and SingularityPRO 4.3.9 / 4.1.14\n\n### Workarounds\n\nIf you do not use the `limit container paths` functionality, then this issue does not affect your installation.\n\nIf you do use the `limit container paths` functionality then you must update. Please also review the documented limitations when user namespaces are enabled [1].",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/sylabs/singularity/v4"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "4.4.2"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/sylabs/singularity"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"last_affected" : "3.1.1"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/sylabs/singularity/security/advisories/GHSA-wqcr-7rf3-f64m"
}, {
"type" : "WEB",
"url" : "https://github.com/sylabs/singularity/commit/c08791793e843d4c9c1f2fc1d9d12abef747378f"
}, {
"type" : "WEB",
"url" : "https://docs.sylabs.io/guides/latest/admin-guide/configfiles.html#limiting-container-execution"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/sylabs/singularity"
}, {
"type" : "WEB",
"url" : "https://github.com/sylabs/singularity/releases/tag/v4.4.2"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-22" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-06-04T17:38:21Z",
"nvd_published_at" : null
}
}