Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Apptainer versions before 1.5.1 incorrectly match paths in the "limit container paths" directive of apptainer.conf, so sibling directories with similar names can be allowed when they should not be. The source does not describe the attacker's access requirements in detail, but the issue applies to setuid-mode installations that use this directive, where a user could run containers from a directory the administrator meant to block. Upgrade to Apptainer 1.5.1 or later. If setuid mode or the limit container paths directive is not used, this issue does not affect the installation.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 4.8 | Medium | 3.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0015, the 4th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:06 UTC First seen by agentprime
- 31 Oct 2026, 15:06 UTC Confirmed by OSV