Directory Traversal Affecting apptainer package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.15% (4th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIANUNSTABLE-APPTAINER-17440185
  • published24 Jun 2026
  • disclosed15 Sept 2026

Introduced: 24 Jun 2026

CVE-2026-48785  (opens in a new tab)
CWE-22  (opens in a new tab)

How to fix?

There is no fixed version for Debian:unstable apptainer.

NVD Description

Note: Versions mentioned in the description apply only to the upstream apptainer package and not the apptainer package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1