Is github.com/sylabs/singularity/v4 4.4 vulnerable?
Go · 3 releases from 4.4.0 to 4.4.2 · latest github.com/sylabs/singularity/v4 is 4.6.0 · checked 20 Nov 2026
Yes: 1 known advisory
Yes. github.com/sylabs/singularity/v4 4.4.2, the last 4.4 release, is affected by 1 known security advisory (1 low), including CVE-2025-64750. 2 more affect earlier 4.4.x releases. At least one has no fixed release yet.
Is your project on an affected github.com/sylabs/singularity/v4?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting github.com/sylabs/singularity/v4 4.4.2
Singularity ineffectively applies of selinux / apparmor LSM process labels in github.com/sylabs/singularity
- Affected
- All versions
- Fixed in
- No fix released
Fixed within 4.4.x, affecting earlier releases
Singularity: Incorrect path matching for 'limit container paths' directive in github.com/sylabs/singularity
- Affected
- <4.4.2
- Fixed in
- 4.4.2
Singluarity: Incorrect path matching for 'limit container paths' directive
- Affected
- <4.4.2
- Fixed in
- 4.4.2
Every github.com/sylabs/singularity/v4 4.4.x release
Affected: 4.4.0 to 4.4.2. Latest github.com/sylabs/singularity/v4: 4.6.0.
| Version | Known advisories |
|---|---|
| github.com/sylabs/singularity/v4 4.4.2 | CVE-2025-64750 |
| github.com/sylabs/singularity/v4 4.4.1 | CVE-2026-47215, CVE-2026-47215, CVE-2025-64750 |
| github.com/sylabs/singularity/v4 4.4.0 | CVE-2026-47215, CVE-2026-47215, CVE-2025-64750 |
Which of your client projects are still on github.com/sylabs/singularity/v4 4.4?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/sylabs/singularity/v4 version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/sylabs/singularity/v4 versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.