Skip to content
Fencer Intel
medium 4.8

CVE-2026-48785 json

Apptainer: Incorrect path matching for 'limit container paths' directive

published 4mo ago modified last mo. also EUVD-2026-78889 , GHSA-cr2j-534f-mf3g , GO-2026-5805

cvss
4.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 4%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/apptainer/apptainer 1.5.1
  • lfprojects apptainer 1.5.1
  • apptainer SLES 15 SP6-LTSS, SLE Module for HPC 15 SP7 1.5.1-150600.4.24.1

suse advisories SUSE-SU-2026:2609-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
  • apptainer openSUSE Tumbleweed 1.5.1-1.1
  • apptainer openSUSE Leap 16.0 1.5.1-bp160.1.1

opensuse advisories openSUSE-SU-2026:21483-1openSUSE-SU-2026:10993-1openSUSE-SU-2026:20942-1

  • apptainer Alpine 3.24 1.5.1-r0

alpine advisories ALPINE-CVE-2026-48785

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2026-48785 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last mo.

Exploit prediction

0.15% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 4.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L
GitHub 3.1 4.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L

Affected packages

ecosystem package affected fixed in
go github.com/apptainer/apptainer
<1.5.1
1.5.1

Affected products

  • apptainer apptainer

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.