medium4.8
CVE-2026-48785
Apptainer has incorrect path matching for 'limit container paths' directive
Impact
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.
Affected packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| go | github.com/apptainer/apptainer | < 1.5.1 | 1.5.1 |
Weakness classification
References
- NVD record
- CVE.org record
- GitHub advisory
- https://github.com/advisories/GHSA-cr2j-534f-mf3g
- https://github.com/apptainer/apptainer/security/advisories/GHSA-cr2j-534f-mf3g
- https://github.com/apptainer/apptainer/commit/0ff35257420e0c6cb97dac11d305749c893e5214
- https://github.com/apptainer/apptainer/pull/3549
- https://github.com/apptainer/apptainer/releases/tag/v1.5.1