CVE-2026-48785

mediumpriority · track · 0EPSS 0.002 · 4 %ileUS
grimoire priorityP3 · Track
Exploitable?
—
no known exploitation
Likely / severe?
0.15% (4th) EPSS
CVSS 4.8 · medium
Is it mine?
1 products
Check your exposure
Who says so?
1 sources
osv

EPSS · scored 2026-10-28

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.

01

cvss

Technical severity, 0–10. One row per scoring source.

4.8
010

base score 0–10 · higher = more severe · hover a vector to decode

v3.14.8mediumCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:Lsecondary · security-advisories@github.comexploitability 1.3 · impact 3.4
v3.14.8mediumCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:Lsecondary · OSV
v3.14.4mediumCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L/E:Usecondary · CVSS-BT (t0sche)
02

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Trackcoordinatorcisa_ssvcUS
03

weaknesses

The CWE weakness classes this flaw belongs to.

04

affected products (1)

Products and version ranges known to be affected.

05

advisories (2)

Vendor and ecosystem advisories describing this.

  • GHSA-cr2j-534f-mf3gApptainer has incorrect path matching for 'limit container paths' directive 2026-06-26ghsa · osvUS

    ### Impact The `limit container paths directive` in `apptainer.conf` is intended to allow a system administrator limit the paths from which containers can be run, under setuid mode. Due to incorrect matching of a path string, sibling directories with similar names may incorrectly be allowed. For example, the configuration: ``` limit container paths = /data/safe ``` Will also allow containers in /data/safe-but-unsafe to be run. ### Patches The issue is patched in apptainer version 1.5.1. ### Workarounds If developers do not use setuid mode or do not use the `limit container paths` functionality, then this issue does not affect their installation. Note that, as documented [1], if user namespaces are allowed for unrestricted use then this functionality does not stop users from running any container of their choice. If developers do use the `limit container paths` functionality they are advised to update. ### Credit This vulnerability was discovered and disclosed to the Apptainer project by Dave Trudgian of Sylabs. ### Resources [1] https://apptainer.org/docs/admin/latest/configfiles.html#limiting-container-execution

  • GO-2026-5805Apptainer has incorrect path matching for 'limit container paths' directive in github.com/apptainer/apptainer2026-07-07vendor · osvUS

    Apptainer has incorrect path matching for 'limit container paths' directive in github.com/apptainer/apptainer

06

also known as (2)

Other names and identifiers for this entity.

07

sources

Which sources assert this record, and when.

published 2026-09-15modified 2026-09-25
09

references (4) nvd

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan