Unrated

Path restriction bypass in SingularityCE/PRO limit container paths

IdentifiersCVE-2026-47215CWE-22

CVE-2026-47215 is an incorrect path matching vulnerability in SingularityCE and SingularityPRO affecting the limit container paths directive. When administrators configure this directive to restrict where containers may be executed from, the path validation logic can incorrectly match similarly named sibling directories. As a result, a container stored in an unintended sibling path with a similar prefix or name can be treated as if it were within an authorized location. The issue is specifically described as affecting path restriction enforcement rather than container image integrity itself.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An attacker or unprivileged user may bypass administrator-defined container path restrictions and execute containers from unauthorized filesystem locations. In setuid mode, this undermines a security boundary intended to constrain which container images or paths are permitted, potentially enabling execution of unapproved or malicious containers from sibling directories that should have been denied. The precise downstream impact depends on local deployment and trust assumptions, but it can defeat policy enforcement and increase risk of unauthorized workload execution.

Mitigation

If you can’t patch tonight, do this now.

If limit container paths is not used, the installation is not affected. Where it is used, apply the vendor-fixed release as the primary mitigation. Additionally, review the documented limitations when user namespaces are enabled, and avoid relying solely on vulnerable path-prefix style restrictions for high-assurance policy enforcement until patched.

Remediation

Patch, then assume compromise.

Upgrade to a fixed version: SingularityCE 4.4.2 or later, SingularityPRO 4.3.9 or 4.1.14 or later, as applicable. After upgrading, verify that limit container paths policies behave as intended and review any existing path-based allowlists for overly broad assumptions.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

SylabsSingularityapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

No public activity tracked yet. Mallory keeps watching.

0 SOURCESView more in app

No public activity observed for this vulnerability.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity