Container execution restriction bypass via prefix matching
Published Sep 15, 2026 · Updated Sep 15, 2026
Path restriction bypass in Apptainer before 1.5.1 allows local users to run containers from unauthorized sibling directories. Image.AuthorizedPath treats the configured allowed path as a plain string prefix instead of enforcing a directory boundary, so a similarly named sibling passes the check. Exploitation requires a local low-privileged account, a setuid installation, configured path limits, and an unauthorized sibling whose name shares an allowed prefix.
Summary
What happened
Path restriction bypass in Apptainer before 1.5.1 allows local users to run containers from unauthorized sibling directories. Image.AuthorizedPath treats the configured allowed path as a plain string prefix instead of enforcing a directory boundary, so a similarly named sibling passes the check. Exploitation requires a local low-privileged account, a setuid installation, configured path limits, and an unauthorized sibling whose name shares an allowed prefix.
The record
- CVE
- CVE-2026-48785
- Published
- Sep 15, 2026
- Updated
- Sep 15, 2026
- Vendor
- Apptainer Project
- Product
- Apptainer
- Classifications
- T1610
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 15, 2026CVE publishedPublication date reported by the CVE source.
- Sep 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.5.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo