Singluarity ineffectively applies selinux / apparmor LSM process labels

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.5 · CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L

EPSS

• CVE-2025-64750: 0.17% estimated exploitation activity in the next 30 days; percentile 6.57 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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:<label or --security apparmor:<profile 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, or that will be specified by the user when running the container. Control of 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. Note that Singularity does…

Published by the source

2 Dec 2025, 21:07 UTC

Last modified by the source

9 Dec 2025, 19:51 UTC

Source last checked

26 Oct 2026, 15:13 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-wwrx-w7c9-rf87

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-64750

Advisory: Singluarity ineffectively applies selinux / apparmor LSM process labels
IDs: CVE-2025-64750, GHSA-wwrx-w7c9-rf87
Record: https://patchnext.com/advisories/cve-2025-64750 (revision 1, source checked 26 Oct 2026, 15:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/sylabs/singularity/v4 4.3.5, 4.1.11. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/sylabs/singularity/v4: affected >= 4.2.0-rc.1, < 4.3.5; < 4.1.11; fixed in 4.1.11, 4.3.5

## Suggested inspection (read-only)
- Go github.com/sylabs/singularity/v4: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/sylabs/singularity/v4.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-wwrx-w7c9-rf87 (GitHub-reviewed advisory GHSA-wwrx-w7c9-rf87 lists affected ranges: Go github.com/sylabs/singularity/v4 >=4.2.0-rc.1 =0 <4.1.11)

Commands are suggestions: review each one before running it.