HighGHSA-pmfr-63c2-jr5cCVE-2020-13845

Execution Control List (ECL) Is Insecure in Singularity

Published 20 Dec 2021 · Updated 8 Jul 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.0.0 <3.6.0
Fixed in
3.6.0
Update to the fixed version for your release line, for example:go get github.com/sylabs/singularity@v3.6.0

Details

Impact

The Singularity Execution Control List (ECL) allows system administrators to set up a policy that defines rules about what signature(s) must be (or must not be) present on a SIF container image for it to be permitted to run.

In Singularity 3.x versions below 3.6.0, the following issues allow the ECL to be bypassed by a malicious user:

  • Image integrity is not validated when an ECL policy is enforced.
  • The fingerprint required by the ECL is compared against the signature object descriptor(s) in the SIF file, rather than to a cryptographically validated signature. Thus, it is trivial to craft an arbitrary payload which will be permitted to run, even if the attacker does not have access to the private key associated with the fingerprint(s) configured in the ECL.

Patches

These issues are addressed in Singularity 3.6.0.

All users are advised to upgrade to 3.6.0. Note that Singularity 3.6.0 uses a new signature format that is necessarily incompatible with Singularity < 3.6.0 - e.g. Singularity 3.5.3 cannot verify containers signed by 3.6.0.

Version 3.6.0 includes a legacyinsecure option that can be set to legacyinsecure = true in ecl.toml to allow the ECL to perform verification of the older, and insecure, legacy signatures for compatibility with existing containers. This does not guarantee that containers have not been modified since signing, due to other issues in the legacy signature format. The option should be used only to temporarily ease the transition to containers signed with the new 3.6.0 signature format.

Workarounds

This issue affects any installation of Singularity configured to use the Execution Control List (ECL) functionality. There is no workaround if ECL is required.

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-pmfr-63c2-jr5c 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-2020-25039Insecure permissions on user namespace / fakeroot temporary rootfs 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.