Back to CVE records
Medium 4.8Published Sep 15, 2026

CVE-2026-47215Singularity: Incorrect path matching for 'limit container paths' directive

Updated under an hour ago ()

Does this affect you?

It affects sylabs singularity and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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.

CVSS
4.8 MEDIUM (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L
Weakness (CWE)
CWE-22
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
GitHub_M
NVD analysis
Awaiting Analysis
Record last updated
Sep 15, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
sylabs singularity
sylabs:singularity (from the name)
before 4.4.2
CNA record
sylabs SingularityPRO
sylabs:singularitypro (from the name)
before 4.1.14; from 4.2.0, < 4.3.9
CNA record

References

  • x-refsource-confirm
  • x-refsource-misc
  • x-refsource-misc
  • x-refsource-misc
  • x-refsource-misc

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.