Sylabs Singularity 3.5.0 through 3.5.3 fails to report an error in a Status Code.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for help- Published
- Jul 14, 2020
- Updated
- Jun 16, 2026
- EPSS
- 1.3% · 70th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.3%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| sylabs | singularity | cpe:2.3:a:sylabs:singularity |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- sylabs singularity3.5.0 and later · up to 3.5.3 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/sylabs/singularity | from 3.5.0 · before 3.6.0 | 3.6.0 |
| openSUSE:Leap 15.1 | singularity | before 3.6.0-lp151.2.6.1 | 3.6.0-lp151.2.6.1 |
| openSUSE:Leap 15.2 | singularity | before 3.6.0-lp152.2.3.1 | 3.6.0-lp152.2.3.1 |
| openSUSE:Tumbleweed | singularity | before 3.8.3-1.2 | 3.8.3-1.2 |
| SUSE:Package Hub 15 SP2 | singularity | before 3.6.0-bp152.2.4.1 | 3.6.0-bp152.2.4.1 |
Same product
sylabs: all recordsOther 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 unsquashfs38Monitor
- CVE-2020-25040Sylabs Singularity through 3.6.2 has Insecure Permissions on temporary directories used in explicit and implicit container build operations,36Monitor
- CVE-2019-11328An issue was discovered in Singularity 3.1.0 to 3.2.0-rc2, a malicious user with local/network access to the host system (e.g.36Monitor
- CVE-2020-25039Sylabs Singularity 3.2.0 through 3.6.2 has Insecure Permissions on temporary directories used in fakeroot or user namespace container execut33Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:github.com/sylabs/singularity | 3.6.0 | Package registry (OSV) |
| opensuse:singularity | 3.6.0-lp152.2.3.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| suse:singularity | 3.6.0-bp152.2.4.1 · SUSE:Package Hub 15 SP2 | Package 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- lists.opensuse.org/opensuse-security-announce/2020-07/msg00046.html
- lists.opensuse.org/opensuse-security-announce/2020-07/msg00059.html
- lists.opensuse.org/opensuse-security-announce/2020-09/msg00053.html
- github.com/hpcng/singularity/security/advisories/GHSA-6w7g-p4jh-rf92
- medium.com/sylabs
Vendor advisories and official records. Exploit/PoC links are deliberately left out.