Quick answers
- Is CVE-2026-48785 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48785 being exploited in the wild.
- How severe is CVE-2026-48785?
- Medium severity, with a CVSS score of 4.8, published 15 September 2026.
- Which products and versions are affected?
- Apptainer < 1.5.1; github.com/apptainer/apptainer (Go) < 1.5.1, SEMVER:introduced=0,fixed=1.5.1.
- Is there a fix for CVE-2026-48785?
- Yes. github.com/apptainer/apptainer (Go): upgrade to 1.5.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-48785 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-48785?
- Check whether you run Apptainer or github.com/apptainer/apptainer (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- github.com/apptainer/apptainer (Go): upgrade to 1.5.1 or later
go get github.com/apptainer/apptainer@v1.5.1
Technical details
A path validation vulnerability exists in Apptainer's 'limit container paths' directive within apptainer.conf. When operating in setuid mode, the software performs incorrect string matching on directory paths, failing to account for trailing slashes or boundary characters. For example, a restriction intended for '/data/safe' would incorrectly match and permit execution from '/data/safe-but-unsafe'. An attacker with local access could exploit this to run containers from unauthorized locations, bypassing administrative execution policies. This issue is resolved in version 1.5.1.
Affected products
- Apptainer Apptainer < 1.5.1
Identifiers
- CVE-2026-48785
- GHSA-cr2j-534f-mf3g
- GO-2026-5805
Timeline
- 2026-06-26: advisory: GitHub Advisory published
- 2026-06-26: disclosed
- 2026-06-04: patched: Version 1.5.1 released