CVE-2025-64750 | Singluarity ineffectively applies of selinux / apparmor LSM process labels

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.

Published: 2025-12-02 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2025-64750 is rated Low Risk (19.2/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.13%). Mandatory action: Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-64750

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.01% 0.13% +0.12%
2 2025-12-03 0.01%

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-64750

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
1.0 3.4 [email protected]

Weakness enumeration for CVE-2025-64750

GitHub Security Advisory for CVE-2025-64750

GHSA-wwrx-w7c9-rf87 · Severity: medium · Ecosystem: go — Singluarity ineffectively applies selinux / apparmor LSM process labels

OS Trackers for CVE-2025-64750

vendor priority summary link
alpine medium CVE-2025-64750: 1 source package rows (singularity); 37 state rows across 3 repos (3.22-community, 3.23-community, edge-community); fixed 2, open 35. https://security.alpinelinux.org/vuln/CVE-2025-64750
debian not yet assigned CVE-2025-64750 not yet assigned priority: Debian including 1 source packages (singularity-container), 1 status rows across 1 suites (sid): open 1. https://security-tracker.debian.org/tracker/CVE-2025-64750
ubuntu medium CVE-2025-64750 medium priority: Ubuntu including 1 source packages (singularity-container), 6 status rows across 6 suites (bionic, jammy, noble, plucky, questing, upstream): needs-triage 4, DNE 1, ignored 1. https://ubuntu.com/security/CVE-2025-64750

Affected software / configurations for CVE-2025-64750

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-64750

cvelogic Threat Intelligence