CVE-2020-13845High· 7.5▾ Twilight

Execution Control List (ECL) Is Insecure in Singularity

▾ Twilight zone — High severity, or a signal on a lesser flaw

Depth score41/ 100 · Moderate

impact 41.3 · likelihood 0.1 · exploitation 0

⚡ Agent-ready:Raw markdown ↗JSON ↗

Proof of concept

Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.

…

Published

Dec 20, 2021

Updated

Jul 8, 2026

CVSS

7.5

Vendor

sylabs

Product

github.com/sylabs/singularity

CWE

—

Depth score

41 · Moderate

EPSS

0.52% · p43

Platforms

—

Source

OSV

Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

EPSS history

Exploit-prediction probability, daily snapshots since Jul 9.

0.5% → 0.5%

Timeline

Disclosure to exploitation, from the record and what we observed since indexing it.

3 events · 1662 days

Dec 20, 2021Published
Disclosed via OSV
Jul 8, 2026Record revised
Last analysed / modified upstream
Jul 9, 2026EPSS first tracked
0.5%

sylabs #osv #go

Affected

github.com/sylabs/singularity >= 3.0.0, < 3.6.0

Patched in

github.com/sylabs/singularity 3.6.0

Full technical detail▾

Overview

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: [email protected]

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

Affected packages

github.com/sylabs/singularity >= 3.0.0, < 3.6.0

Remediation

Upgrade to a patched release:

github.com/sylabs/singularity 3.6.0

References

Related vulnerabilities

Connected by shared product, vendor, weakness, or advisory.

#osv#go

← Back to feed