github.com/sylabs/singularity/v4 vulnerabilities

Registry
Go
Latest
4.6.0

4 known advisories

The latest version, 4.6.0, is affected by 1 of them.

Is your project on an affected github.com/sylabs/singularity/v4?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Security advisories for github.com/sylabs/singularity/v4

  • LowCVE-2026-47215GO-2026-571525 Jun 2026

    Singularity: Incorrect path matching for 'limit container paths' directive in github.com/sylabs/singularity

    Affected
    <4.4.2
    Fixed in
    4.4.2
  • MediumCVE-2026-47215GHSA-wqcr-7rf3-f64m4 Jun 2026

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

    Affected
    <4.4.2
    Fixed in
    4.4.2
  • LowCVE-2025-64750GO-2025-41778 Dec 2025

    Singularity ineffectively applies of selinux / apparmor LSM process labels in github.com/sylabs/singularity

    Affected
    All versions
    Fixed in
    No fix released
  • MediumCVE-2025-64750GHSA-wwrx-w7c9-rf872 Dec 2025

    Singluarity ineffectively applies selinux / apparmor LSM process labels

    Affected
    >=4.2.0-rc.1 <4.3.5 · <4.1.11
    Fixed in
    4.1.11, 4.3.5

Is your github.com/sylabs/singularity/v4 version vulnerable?

Which of your client projects still run an old github.com/sylabs/singularity/v4?

NPMscan reads the go.mod in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other Go packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Go registry.