Vulnerabilities in pkg:golang/github.com/sylabs/singularity

PACKAGE
Advisory Identifier: GHSA-wqcr-7rf3-f64m
Advisory Summary

CVE-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.

10 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:golang/github.com/sylabs/singularity

10 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:golang/github.com/sylabs/singularity. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-wqcr-7rf3-f64m CVE-2026-47215 MODERATE Singluarity: Incorrect path matching for 'limit container paths' directive
GHSA-p83v-8vmr-qfv9 CVE-2018-19295 HIGH Sylabs Singularity Improper Input Validation
GHSA-mj73-5x75-9phh CVE-2019-19724 HIGH Singularity insecure permissions
GHSA-557g-r22w-9wvx CVE-2019-11328 HIGH Incorrect Permission Assignment for Critical Resource in Singularity
GHSA-6w7g-p4jh-rf92 CVE-2020-13846 HIGH "Verify All" Returns Success Despite Validation Failures in Singularity
GHSA-pmfr-63c2-jr5c CVE-2020-13845 HIGH Execution Control List (ECL) Is Insecure in Singularity
GHSA-5mv9-q7fq-9394 CVE-2021-32635 MODERATE Action Commands (run/shell/exec) Against Library URIs Ignore Configured Remote Endpoint
GHSA-w6v2-qchm-grj7 CVE-2020-25039 HIGH Insecure permissions on user namespace / fakeroot temporary rootfs in Singularity
GHSA-jv9c-w74q-6762 CVE-2020-25040 HIGH Insecure permissions on build temporary rootfs in Singularity
GHSA-7gcp-w6ww-2xv9 CVE-2020-15229 HIGH Path traversal and files overwrite with unsquashfs in singularity

CVE-2026-47215 at a Glance

CVE Identifier CVE-2026-47215
GHSA Identifier GHSA-wqcr-7rf3-f64m
Severity MODERATE
CVSS v3.1 Base Score 4.8
CWE Classification CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Affected Product Singluarity
Package Ecosystem Go
Published Date
Last Updated

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).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity Low (I:L)
Availability Low (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.

github.com/sylabs/singularity/v4 fixed: 4.4.2
Upgrade github.com/sylabs/singularity/v4 to 4.4.2
github.com/sylabs/singularity fixed: Latest secure release
Upgrade github.com/sylabs/singularity to Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/sylabs/singularity/v4

How 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/v4

Analyze 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

### 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].

CVE-2026-47215 Affected Singluarity Versions

2 component(s)
Fixed Versions:
4.4.2
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?
CVE-2026-47215 is a security vulnerability in Singluarity involving Incorrect path matching for 'limit container paths' directive under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').
Which Singluarity versions are affected?
Affected versions include releases prior to 4.4.2 across affected packages: github.com/sylabs/singularity/v4, github.com/sylabs/singularity.
What version fixes CVE-2026-47215?
Upgrading to 4.4.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/sylabs/singularity/v4 affected?
Yes, github.com/sylabs/singularity/v4 is affected in releases prior to 4.4.2. Upgrade your dependency to 4.4.2 or later.
Is github.com/sylabs/singularity affected?
Yes, github.com/sylabs/singularity is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2026-47215?
CVE-2026-47215 has a CVSS v3.1 base score of 4.8 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L.
What CWE is associated with CVE-2026-47215?
CVE-2026-47215 is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (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.).
How can I check Go dependencies for CVE-2026-47215?
Run the dependency tree command: 'inspect dependencies for github.com/sylabs/singularity/v4'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "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
  }
}