Unrated

Apptainer limit container paths path-matching bypass in setuid mode

IdentifiersCVE-2026-48785CWE-22

CVE-2026-48785 is an incorrect path matching vulnerability in Apptainer affecting the 'limit container paths' directive when Apptainer is used in setuid mode. Due to flawed path validation or matching logic, Apptainer can incorrectly treat similarly named sibling directories as matching an allowed path, allowing a container image to be executed from an unintended location. The issue weakens administrator-enforced restrictions intended to limit which filesystem paths may be used for container execution.

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.

Successful exploitation allows an attacker or unauthorized local user to bypass the 'limit container paths' restriction and run containers from unintended sibling directories with similar names. This undermines policy enforcement around approved container locations in setuid deployments and may permit execution of unapproved or attacker-controlled container images despite administrative restrictions.

Mitigation

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

The issue does not affect installations that do not use setuid mode or do not use the 'limit container paths' functionality. As an interim measure, administrators should avoid relying solely on this directive for containment in affected versions and should update affected systems. Per the vendor documentation, if user namespaces are allowed for unrestricted use, this functionality does not prevent users from running arbitrary containers.

Remediation

Patch, then assume compromise.

Upgrade Apptainer to version 1.5.1 or later, which fixes the incorrect path matching behavior in the 'limit container paths' directive.

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.

ACTIVITY FEED

Recent activity

1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

1 SOURCESView more in app

No news coverage yet. Advisories and community discussion only.

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 activity1