Skip to content
Noroxi
NVD / CVE Program· CNA mitre

CVE-2020-25039: Sylabs Singularity 3.2.0 through 3.6.2 has Insecure Permissions on temporary directories used in fakeroot or user namespace container…

HighCVSS 8.1 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 33/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 2% (FIRST EPSS); higher than 81.1% of all records.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: singularity (Alpine:v3.19) 3.6.3-r0; github.com/sylabs/singularity (Go) 3.6.3; singularity (openSUSE:Leap 15.1) 3.6.3-lp152.2.6.1.

Low priority for now. Upgrade to singularity (Alpine:v3.19) 3.6.3-r0; github.com/sylabs/singularity (Go) 3.6.3; singularity (openSUSE:Leap 15.1) 3.6.3-lp152.2.6.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Sylabs Singularity 3.2.0 through 3.6.2 has Insecure Permissions on temporary directories used in fakeroot or user namespace container execution.

Published
Sep 16, 2020
Updated
Jun 16, 2026
EPSS
2.0% · 81th percentile

Report tools

JSON

Action score

33

Monitor

Low priority for now.

CVSS
32 / 40 · 8.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.0%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2020-25039

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for sylabs records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
sylabssingularity
opensuseleap

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • opensuse leap15.1
  • opensuse leap15.2
  • sylabs singularity3.2.0 and later · up to 3.6.2 inclusive

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.19singularityfrom 3.2.0 · before 3.6.3-r03.6.3-r0
Gogithub.com/sylabs/singularityfrom 3.2.0 · before 3.6.33.6.3
openSUSE:Leap 15.1singularitybefore 3.6.3-lp152.2.6.13.6.3-lp152.2.6.1
openSUSE:Tumbleweedsingularitybefore 3.8.3-1.23.8.3-1.2
SUSE:Package Hub 15 SP2singularitybefore 3.6.3-bp152.2.8.13.6.3-bp152.2.8.1

Same product

sylabs: all records

Other highest-scoring records for the same primary product.

  • CVE-2021-33027Sylabs Singularity Enterprise through 1.6.2 has Insufficient Entropy in a nonce.
    39Monitor
  • CVE-2021-33622Sylabs Singularity 3.5.x and 3.6.x, and SingularityPRO before 3.5-8, has an Incorrect Check of a Function's Return Value.
    39Monitor
  • CVE-2020-15229Path traversal and files overwrite with unsquashfs
    38Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2020-13846Jul 14, 2020 · Sylabs Singularity 3.5.0 through 3.5.3 fails to report an error in a Status Code.
    30Monitor
  • ← EarlierCVE-2020-13847Jul 14, 2020 · Sylabs Singularity 3.0 through 3.5 lacks support for an Integrity Check.
    30Monitor
  • Later →CVE-2020-25040Sep 16, 2020 · Sylabs Singularity through 3.6.2 has Insecure Permissions on temporary directories used in explicit and implicit container build…
    36Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:singularity3.6.3-r0 · Alpine:v3.19Package registry (OSV)
Go:github.com/sylabs/singularity3.6.3Package registry (OSV)
opensuse:singularity3.6.3-lp152.2.6.1 · openSUSE:Leap 15.1Package registry (OSV)
suse:singularity3.6.3-bp152.2.8.1 · SUSE:Package Hub 15 SP2Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
None

Weakness class (CWE)

CWE-668 · Exposure of Resource to Wrong Sphere

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records