SingularityCE and SingularityPRO are open source container platforms. Prior to SingularityCE 4.4.2 and SingularityPRO 4.3.9 and 4.1.14, incorrect path-string matching in the singularity.conf limit container paths directive allows a container in a sibling directory such as /data/safe-but-unsafe to be run when /data/safe is allowed under setuid mode. This permits a user to run a container from outside the administrator's configured path allowlist. Installations that do not use limit container paths are not affected. This issue is fixed in SingularityCE 4.4.2 and SingularityPRO 4.3.9 and 4.1.14.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - SingularityCE and SingularityPRO are open source container platforms. Prior to SingularityCE 4.4.2 and     SingularityPRO 4.3.9 and 4.1.14, incorrect path-string matching in the singularity.conf limit container     paths directive allows a container in a sibling directory such as /data/safe-but-unsafe to be run when     /data/safe is allowed under setuid mode. This permits a user to run a container from outside the     administrator's configured path allowlist. Installations that do not use limit container paths are not     affected. This issue is fixed in SingularityCE 4.4.2 and SingularityPRO 4.3.9 and 4.1.14. (CVE-2026-47215)

Note that Nessus relies on the presence of the package as reported by the vendor.

The remote Fedora 45 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2026-d32912dc74 advisory.

    Automatic update for singularity-ce-4.4.2-1.fc45.

    ##### **Changelog**

    ```
    * Wed Jun 10 2026 David Trudgian <dtrudg@sylabs.io> - 4.4.2-1
    - Upgrade to 4.4.2 upstream version.
    - Fix rhbz#2453093
    - Fix rhbz#2458933
    - Fix CVE-2026-47215

    ```

Tenable has extracted the preceding description block directly from the Fedora security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - SingularityCE and SingularityPRO are open source container platforms. Prior to SingularityCE 4.4.2 and
    SingularityPRO 4.3.9 and 4.1.14, incorrect path-string matching in the singularity.conf limit container
    paths directive allows a container in a sibling directory such as /data/safe-but-unsafe to be run when
    /data/safe is allowed under setuid mode. This permits a user to run a container from outside the
    administrator's configured path allowlist. Installations that do not use limit container paths are not
    affected. This issue is fixed in SingularityCE 4.4.2 and SingularityPRO 4.3.9 and 4.1.14. (CVE-2026-47215)

ID	Name	Product	Family	Type	Severity
346964	Linux Distros Unpatched Vulnerability : CVE-2026-47215	Nessus	Misc.	Local	medium
320446	Fedora 45 : singularity-ce (2026-d32912dc74)	Nessus	Fedora Local Security Checks	Local	high
442631	SCA: security update for github.com/sylabs/singularity/v4 (GHSA-wqcr-7rf3-f64m)	Tenable Cloud Security	SCA Checks	Local	medium
442631	SCA: security update for github.com/sylabs/singularity/v4 (GHSA-wqcr-7rf3-f64m)	Tenable Self-Hosted Container Security	SCA Checks	Local	medium

Detections

Analytics

CVE-2026-47215

medium

Tenable Plugins

medium

high

medium

medium