CVE-2025-64750
published 2025-12-02CVE-2025-64750: SingularityCE and SingularityPRO are open source container platforms. Prior to SingularityCE 4.3.5 and SingularityPRO 4.1.11 and 4.3.5, if a user relies on LSM…
PriorityP421medium4.5CVSS 3.1
AVLACHPRNUIRSUCLILAL
EPSS
0.14%
3.5th percentile
SingularityCE and SingularityPRO are open source container platforms. Prior to SingularityCE 4.3.5 and SingularityPRO 4.1.11 and 4.3.5, if a user relies on LSM restrictions to prevent malicious operations then, under certain circumstances, an attacker can redirect the LSM label write operation so that it is ineffective. The attacker must cause the user to run a malicious container image that redirects the mount of /proc to the destination of a shared mount, either known to be configured on the target system, or that will be specified by the user when running the container. The attacker must also control the content of the shared mount, for example through another malicious container which also binds it, or as a user with relevant permissions on the host system it is bound from. This vulnerability is fixed in SingularityCE 4.3.5 and SingularityPRO 4.1.11 and 4.3.5.
Affected
5 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | singularity-container | — | — |
| github.com | sylabs_singularity_v4 | >= 0 < 4.1.11 | 4.1.11 |
| github.com | sylabs_singularity_v4 | >= 4.2.0-rc.1 < 4.3.5 | 4.3.5 |
| sylabs | singularity | < 4.1.11 | 4.1.11 |
| sylabs | singularity | — | — |
CVSS provenance
nvdv3.14.5MEDIUMCVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L
ghsa7.3HIGH
osv7.3HIGH
vendor_debian4.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Debian
CVE-2025-64750: singularity-container - SingularityCE and SingularityPRO are open source container platforms. Prior to S...
vendor_debian·2025·CVSS 4.5
CVE-2025-64750 [MEDIUM] CVE-2025-64750: singularity-container - SingularityCE and SingularityPRO are open source container platforms. Prior to S...
SingularityCE and SingularityPRO are open source container platforms. Prior to SingularityCE 4.3.5 and SingularityPRO 4.1.11 and 4.3.5, if a user relies on LSM restrictions to prevent malicious operations then, under certain circumstances, an attacker can redirect the LSM label write operation so that it is ineffective. The attacker must cause the user to run a malicious container image that redirects the mount of /proc to the destination of a shared mount, either known to be configured on the target system, or that will be specified by the user when running the container. The attacker must also control the content of the shared mount, for example through another malicious container which also binds it, or as a user with relevant permissions on the host system it is bound from. This vulner
OSV
Singularity ineffectively applies of selinux / apparmor LSM process labels in github.com/sylabs/singularity
osv·2025-12-08
CVE-2025-64750 Singularity ineffectively applies of selinux / apparmor LSM process labels in github.com/sylabs/singularity
Singularity ineffectively applies of selinux / apparmor LSM process labels in github.com/sylabs/singularity
Singularity ineffectively applies of selinux / apparmor LSM process labels in github.com/sylabs/singularity.
NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.
(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)
The additional affected modules and versions are: github.com/sylabs/singularity/v4 before v4.1.11.
GHSA
Singluarity ineffectively applies selinux / apparmor LSM process labels
ghsa·2025-12-02·CVSS 7.3
CVE-2025-64750 [HIGH] CWE-61 Singluarity ineffectively applies selinux / apparmor LSM process labels
Singluarity ineffectively applies selinux / apparmor LSM process labels
### Impact
_**Native Mode (default)**_
Singularity's default native runtime allows users to apply restrictions to container processes using the apparmor or selinux Linux Security Modules (LSMs), via the `--security selinux:` or `--security apparmor:` flags.
LSM labels are written to process or thread `attrs/exec` under `/proc`. If a user relies on LSM restrictions to prevent malicious operations then, under certain circumstances, an attacker can redirect the LSM label write operation so that it is ineffective. This requires:
* The attacker to cause the user to run a malicious container image that redirects the mount of `/proc` to the destination of a shared mount, either known to be configured on the target system
OSV
Singluarity ineffectively applies selinux / apparmor LSM process labels
osv·2025-12-02·CVSS 7.3
CVE-2025-64750 [HIGH] Singluarity ineffectively applies selinux / apparmor LSM process labels
Singluarity ineffectively applies selinux / apparmor LSM process labels
### Impact
_**Native Mode (default)**_
Singularity's default native runtime allows users to apply restrictions to container processes using the apparmor or selinux Linux Security Modules (LSMs), via the `--security selinux:` or `--security apparmor:` flags.
LSM labels are written to process or thread `attrs/exec` under `/proc`. If a user relies on LSM restrictions to prevent malicious operations then, under certain circumstances, an attacker can redirect the LSM label write operation so that it is ineffective. This requires:
* The attacker to cause the user to run a malicious container image that redirects the mount of `/proc` to the destination of a shared mount, either known to be configured on the target system
OSV
CVE-2025-64750: SingularityCE and SingularityPRO are open source container platforms
osv·2025-12-02·CVSS 4.5
CVE-2025-64750 [MEDIUM] CVE-2025-64750: SingularityCE and SingularityPRO are open source container platforms
SingularityCE and SingularityPRO are open source container platforms. Prior to SingularityCE 4.3.5 and SingularityPRO 4.1.11 and 4.3.5, if a user relies on LSM restrictions to prevent malicious operations then, under certain circumstances, an attacker can redirect the LSM label write operation so that it is ineffective. The attacker must cause the user to run a malicious container image that redirects the mount of /proc to the destination of a shared mount, either known to be configured on the target system, or that will be specified by the user when running the container. The attacker must also control the content of the shared mount, for example through another malicious container which also binds it, or as a user with relevant permissions on the host system it is bound from. This vulner
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://github.com/advisories/GHSA-fh74-hm69-rqjwhttps://github.com/opencontainers/runc/security/advisories/GHSA-cgrx-mc8f-2prmhttps://github.com/sylabs/singularity/commit/27882963879a7af1699fd6511c3f5f1371d80f33https://github.com/sylabs/singularity/commit/5af3e790c40593591dfc26d0692e4d4b21c29ba0https://github.com/sylabs/singularity/pull/3850https://github.com/sylabs/singularity/security/advisories/GHSA-wwrx-w7c9-rf87
2025-12-02
Published