HighGHSA-w6v2-qchm-grj7CVE-2020-25039

Insecure permissions on user namespace / fakeroot temporary rootfs in Singularity

Published 20 Dec 2021 · Updated 10 Sept 2026

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

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

Affected package

Affected
>=3.2.0 <3.6.3
Fixed in
3.6.3
Update to the fixed version for your release line, for example:go get github.com/sylabs/singularity@v3.6.3

Details

Impact

Insecure permissions on temporary directories used in fakeroot or user namespace container execution.

When a Singularity action command (run, shell, exec) is run with the fakeroot or user namespace option, Singularity will extract a container image to a temporary sandbox directory. Due to insecure permissions on the temporary directory it is possible for any user with access to the system to read the contents of the image. Additionally, if the image contains a world-writable file or directory, it is possible for a user to inject arbitrary content into the running container.

Patches

This issue is addressed in Singularity 3.6.3.

All users are advised to upgrade to 3.6.3.

Workarounds

The issue is mitigated if TMPDIR is set to a location that is only accessible to the user, as any subdirectories directly under TMPDIR cannot then be accessed by others. However, this is difficult to enforce so it is not recommended to rely on this as a mitigation.

For more information

General questions about the impact of the advisory / changes made in the 3.6.0 release can be asked in the:

Any sensitive security concerns should be directed to: security@sylabs.io

See our Security Policy here: https://sylabs.io/security-policy

Is GHSA-w6v2-qchm-grj7 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/sylabs/singularity, and gives you the command that fixes it.

More advisories for github.com/sylabs/singularity

  • LowCVE-2026-47215Singularity: Incorrect path matching for 'limit container paths' directive in github.com/sylabs/singularity · 25 Jun 2026
  • MediumCVE-2026-47215Singluarity: Incorrect path matching for 'limit container paths' directive · 4 Jun 2026
  • LowCVE-2025-64750Singularity ineffectively applies of selinux / apparmor LSM process labels in github.com/sylabs/singularity · 8 Dec 2025
  • HighCVE-2019-19724Singularity insecure permissions · 24 May 2022
  • HighCVE-2018-19295Sylabs Singularity Improper Input Validation · 14 May 2022
  • HighCVE-2019-11328Incorrect Permission Assignment for Critical Resource in Singularity · 20 Dec 2021
All 12 advisories for github.com/sylabs/singularity

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.