# CVE-2025-64750: GO-2025-4177 - Singularity ineffectively applies of selinux / apparmor LSM process labels in github.com/sylabs/singularity

Source: https://junglewise.ai/threats/cve-2025-64750-singluarity-ineffectively-applies-selinux-apparmor-lsm-process  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2025-12-02  
License: CC BY 4.0 with a link back

CVE-2025-64750 · Severity: medium · CVSS 4.5 · Published 2025-12-02

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.

Technologies: [github.com/sylabs/singularity (Go)](https://junglewise.ai/threats/technologies/github-com-sylabs-singularity). Vendors: [Go](https://junglewise.ai/threats/vendors/go).

## Quick answers

**Is CVE-2025-64750 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2025-64750 being exploited in the wild.

**How severe is CVE-2025-64750?** Medium severity, with a CVSS score of 4.5, published 2 December 2025.

**Which products and versions are affected?** github.com/sylabs/singularity (Go) SEMVER:introduced=0; github.com/sylabs/singularity/v4 (Go) SEMVER:introduced=0, SEMVER:introduced=4.2.0-rc.1,fixed=4.3.5.

**Is there a fix for CVE-2025-64750?** Yes. github.com/sylabs/singularity/v4 (Go): upgrade to 4.3.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2025-64750?** Check whether you run github.com/sylabs/singularity (Go) or github.com/sylabs/singularity/v4 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/sylabs/singularity/v4 (Go): upgrade to 4.3.5 or later

  ```sh
  go get github.com/sylabs/singularity/v4@v4.3.5
  ```


## Affected products

- github.com/sylabs/singularity (Go) SEMVER:introduced=0
- github.com/sylabs/singularity/v4 (Go) SEMVER:introduced=0, SEMVER:introduced=4.2.0-rc.1,fixed=4.3.5

## Identifiers

- CVE-2025-64750
- GHSA-wwrx-w7c9-rf87
- GO-2025-4177

## Related threats

- [Sylabs Singularity incorrect path matching in limit container paths](https://junglewise.ai/threats/cve-2026-47215-sylabs-singularity-incorrect-path-matching-in-limit-container)
- [Singularity insecure permissions](https://junglewise.ai/threats/cve-2019-19724-singularity-insecure-permissions)
- [Sylabs Singularity Improper Input Validation](https://junglewise.ai/threats/cve-2018-19295-sylabs-singularity-improper-input-validation)
- [Insecure permissions on user namespace / fakeroot temporary rootfs in Singularity](https://junglewise.ai/threats/cve-2020-25039-insecure-permissions-on-user-namespace-fakeroot-temporary-rootfs)
- [Incorrect Permission Assignment for Critical Resource in Singularity](https://junglewise.ai/threats/cve-2019-11328-incorrect-permission-assignment-for-critical-resource-in)