CVE-2026-48785 Apptainer: Incorrect path matching for 'limit container paths' directive
Local users can bypass container path restrictions in setuid mode due to flawed prefix matching, allowing execution of unauthorized containers.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-48785?
CVE-2026-48785 is a medium-severity path traversal vulnerability in apptainer, published on 15 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Official description
Apptainer is an open source container platform. Prior to version 1.5.1, Image.AuthorizedPath applies plain string-prefix matching to the limit container paths directive in apptainer.conf, so an allowed path such as /data/safe also authorizes a sibling path such as /data/safe-but-unsafe. A local user can consequently run a container from a directory outside the administrator's intended allowlist when Apptainer operates in setuid mode. Installations that do not use setuid mode or do not configure limit container paths are not affected, and unrestricted user namespaces already allow users to run containers of their choice. This issue is fixed in version 1.5.1.
Weakness: CWE-22
Which versions are affected by CVE-2026-48785?
3 open source packages ship an affected version, including github.com/apptainer/apptainer.
| Package | Affected | Fixed in |
|---|---|---|
github.com/apptainer/apptainer Go | All versions | 1.5.1 |
github.com/apptainer/apptainer Go | All versions | 1.5.1 |
github.com/apptainer/apptainer Go | All versions | 1.5.1 |
Linux distribution packages (2)
apptainer openSUSE:Leap 16.0 | All versions | 1.5.1-bp160.1.1 |
apptainer openSUSE:Tumbleweed | All versions | 1.5.1-1.1 |
How do I fix CVE-2026-48785?
Upgrade github.com/apptainer/apptainer to 1.5.1 or later.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2026-48785 being exploited?
There is no known exploitation of CVE-2026-48785 in the wild and no public exploit code.
Sources
Also known as GHSA-cr2j-534f-mf3g, GO-2026-5805, UBUNTU-CVE-2026-48785, openSUSE-SU-2026:10993-1, openSUSE-SU-2026:20942-1.