{
  "document": {
    "aggregate_severity": {
      "namespace": "https://www.suse.com/support/security/rating/",
      "text": "moderate"
    },
    "category": "csaf_security_advisory",
    "csaf_version": "2.0",
    "distribution": {
      "text": "Copyright 2024 SUSE LLC. All rights reserved.",
      "tlp": {
        "label": "WHITE",
        "url": "https://www.first.org/tlp/"
      }
    },
    "lang": "en",
    "notes": [
      {
        "category": "summary",
        "text": "Security update for apptainer",
        "title": "Title of the patch"
      },
      {
        "category": "description",
        "text": "This update for apptainer fixes the following issues:\n\nChanges in apptainer:\n\n- Update apptainer to version v1.5.1\n  * Security fix (bsc#1267982):\n    Fix for CVE-2026-48785 / GHSA-cr2j-534f-mf3g. Incorrect path\n    matching for limit container paths directive. This is only\n    applicable to SUID installations that have paths listed in\n    limit container paths that are string prefixes of other paths\n    which are not desired to be included in the list. For example,\n    if /scratch is in the list but `/scratch2` also exists and contains\n    container images, previously the latter would match but now\n    only images under the exactly matching `/scratch` are included.\n  Other changes:\n  * Work around segmentation fault sometimes seen while `mksquashfs`\n    under proot is creating a SIF file.\n  * Update bundled PRoot to version 5.4.0-rootless.3 in order to\n    fix a problem where SIF files could be corrupted when\n    `mksquashfs` died with a signal. The proot command was not\n    passing back an error exit code.\n  * Updated bundled `squashfuse_ll` to version 0.6.2 in order to\n    fix a crash sometimes seen with apptainer in unprivileged\n    docker.\n  * Update bundled fuse2fs to version 1.47.4 instead of patching\n    the bugs in 1.47.3.\n  * Fix a crash that happened when `/etc/resolv.conf` was a\n    symlink while building from a definition file using the\n    localimage bootstrap.\n  * Support hosts that have an /etc/resolv.conf symlink pointing\n    to `../run` in addition to `/run`.\n  * Change the download-dependencies script to skip downloading\n    the PRoot source code on architectures that it is known to\n    not support (that is: ppc*, s390*, and riscv*).\n    In those situations Apptainer will skip trying to compile\n    and run proot. As a result original owners and groups of\n    files will not be preserved in SIF images built by\n    unprivileged users, as was the case for all architectures\n    prior to 1.5.0.\n  * Fix panic encountered during progress bar update while\n    pulling image.\n  * Fix fakeroot overwriting root\u0027s username in `/etc/passwd`\n    with the host user\u0027s name, a regression introduced in v1.5.0.\n  * Add nonested flag for --mount specifications to prevent\n    individual bind mounts from being passed to nested containers\n    via `APPTAINER_BIND`.\n    Example: `--mount type=bind,source=/data,destination=/mnt,nonested`.\n- Changes from version v1.5.0:\n   New Features \u0026 Functionalities\n   * Add support for a subset of the Container Device Interface\n     (CDI) standard through new `--device` and\n     `--cdi-dirs run/shell/exec` options. Honors environment\n     variable settings, bind mounts, and device files listed in\n     CDI specification files.\n   * Add support for selective mounting of Intel(R) Gaudi\n     accelerators. This feature is only for use in combination\n     with a minimal /dev directory, selected either with the\n     `--contain` flag or by configuring mount dev with the minimal\n     option; otherwise all the devices are available anyway. This\n     feature is enabled via the `--intel-hpu option` and by\n     specifying the HABANA_VISIBLE_DEVICES environment variable,\n     which should contain a comma-separated list of device IDs\n     (e.g., \"1,2,3\") or \"all\" to import all of them.\n     The default if `HABANA_VISIBLE_DEVICES` is not set is \"all\".\n   * Add support for downloading SIF images from an IPFS\n     peer-to-peer cluster using an HTTP gateway (similar to the\n     existing support for IPFS in the curl tool). The address of\n     the gateway can be set in the `IPFS_GATEWAY` environment\n     variable or read from ~/.ipfs/gateway or /etc/ipfs/gateway.\n   * Add `--no-env` action and instance option and corresponding\n     `APPTAINER_NOENV` environment variable that can provide a\n     comma-separated list of environment variables to skip\n     importing from the host environment into the container.\n   * Add `--data` build option which creates a SIF file with\n     a squashfs data partition instead of a code partition,\n     given an existing squashfs file as the source.\n   * If `PREPEND_LD_LIBRARY_PATH` is set in the container\n     environment (through an `--env` option, an `APPTAINERENV_`\n     prefix from the host, or in the container definition)\n     then prepend that string to `:$LD_LIBRARY_PATH`. Likewise\n     if `APPEND_LD_LIBRARY_PATH` is set in the container\n     environment then append that string to `$LD_LIBRARY_PATH:`.\n     This is only done when `LD_LIBRARY_PATH` is set, although\n     if the container is based on glibc, when `LD_LIBRARY_PATH`\n     is not set it will first be filled with the default\n     library search path as found through ldconfig.\n   * Create reproducible SIF images, if the environment variable\n     `SOURCE_DATE_EPOCH` has been set (as a Unix timestamp given\n     as seconds since the beginning of 1970, in the UTC timezone).\n     Also add `--reproducible` flag to build and pull from\n     `oras://` sources. This sets `SOURCE_DATE_EPOCH`\n     automatically from the image \"created\" time.\n   * Support hosts that have `/etc/resolv.conf` pointing to a\n     symlink under /run, such as those hosts that are running\n     systemd-resolved. In this case, the symlink is copied into\n     the container and the parent directory of the target of the\n     symlink is bind-mounted from the host. The result is that\n     even if the target of the symlink is replaced with a new file,\n     the container sees the update in `/etc/resolv.conf`.\n   * Add `/etc/resolv.conf` to the list of host paths that can be\n     prevented from automatic import into the container with the\n     `--no-mount` option.\n   * Preserve owner and group information on files in containers\n     downloaded from OCI registries when building SIF files, even\n     for unprivileged users. This takes advantage of the fact that\n     the library (umoci) that downloads containers preserves owner\n     and group information in an extended attribute. Adds bundled\n     tool proot which is modified from the upstream tool by the\n     rootless-containers project to make the owner and group appear\n     to be in the ordinary `stat()` information. That tool is now\n     used when invoking mksquashfs to create the filesystem\n     partition in a SIF file. It can be disabled with the hidden\n     build option `--ignore-proot`.\n   * When unsquashing an image while running under a root-mapped\n     user namespace (such as when using fakeroot without subuid\n     mapping), insert another namespace mapping back to the\n     original user so unsquashfs doesn\u0027t try (and fail) to change\n     the owner and group information on the unpacked files.\n   * Record image digest metadata (sha256 from RepoDigests), for\n     OCI registry images. Also add the image name (ref) of the\n     image from \"docker\", with registry and tag. This is useful\n     for traceability, when using docker.io or a tag like latest.\n     Unfortunately the feature does not work with \"docker-archive\"\n     or \"docker-daemon\".\n   * Apptainer now supports the `loong64` architecture.\n   Changed defaults / behaviours\n   * If libraries are bound in to `/.singularity.d/libs` (such as\n     with GPU options like `--nv`) and the container is based on\n     glibc and `LD_LIBRARY_PATH` is not already set, it is now set\n     to the default library search path. Since `/.singularity.d/libs`\n    is appended to `LD_LIBRARY_PATH`, this makes libraries\n    installed in the container take precedence over libraries\n    bound in from the host. This reduces the chances of mismatched\n    glibc versions. However, if there are indeed libraries on the\n    host that need to take precedence over libraries in the\n    container, that can be forced with\n    `PREPEND_LD_LIBRARY_PATH=/.singularity.d/libs`.\n  * Change the default arm variant to v7, and stop using the GOARM\n    environment variable. The variables GOOS, GOARCH and GOARM\n    are only used when building.\n  * The oras transport now supports architectures beyond amd64.\n    Images downloaded from oras without using the cache are now\n    checksummed. A progress bar is shown during the process.\n    Add support for APPTAINER_TMPDIR to the commands apptainer\n    overlay create and apptainer plugin compile.\n  Bug Fixes:\n   * Make the root default capabilities configuration option apply\n     only to the real root user as documented and not to a\n     fakeroot user.\n   * Fix long-time bug in importing environment variables from oci\n     containers (defined by `ENV` in their definition file) with\n     shell characters in them. It now escapes them with single\n     backslashes instead of double backslashes so they behave\n     like they do in podman and docker.\n   * The username in `/etc/passwd` inside a container now always\n     corresponds to the username of the user on the host even if\n     an entry with the same UID is found in the container.\n   * When apptainer reinvokes itself on behalf of the run-help\n     command, it passes through `LD_LIBRARY_PATH`. This makes it\n     work correctly when it was installed with\n     `install-unprivileged.sh` on a host operating system that\u0027s\n     different than the one the installed binaries were built on.\n",
        "title": "Description of the patch"
      },
      {
        "category": "details",
        "text": "openSUSE-Leap-16.0-packagehub-310",
        "title": "Patchnames"
      },
      {
        "category": "legal_disclaimer",
        "text": "CSAF 2.0 data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0).",
        "title": "Terms of use"
      }
    ],
    "publisher": {
      "category": "vendor",
      "contact_details": "https://www.suse.com/support/security/contact/",
      "name": "SUSE Product Security Team",
      "namespace": "https://www.suse.com/"
    },
    "references": [
      {
        "category": "external",
        "summary": "SUSE ratings",
        "url": "https://www.suse.com/support/security/rating/"
      },
      {
        "category": "self",
        "summary": "URL of this CSAF notice",
        "url": "https://ftp.suse.com/pub/projects/security/csaf/opensuse-su-2026_20942-1.json"
      },
      {
        "category": "self",
        "summary": "SUSE Bug 1267982",
        "url": "https://bugzilla.suse.com/1267982"
      },
      {
        "category": "self",
        "summary": "SUSE CVE CVE-2026-48785 page",
        "url": "https://www.suse.com/security/cve/CVE-2026-48785/"
      }
    ],
    "title": "Security update for apptainer",
    "tracking": {
      "current_release_date": "2026-09-17T17:34:45Z",
      "generator": {
        "date": "2026-06-10T14:46:21Z",
        "engine": {
          "name": "cve-database.git:bin/generate-csaf.pl",
          "version": "1"
        }
      },
      "id": "openSUSE-SU-2026:20942-1",
      "initial_release_date": "2026-06-10T14:46:21Z",
      "revision_history": [
        {
          "date": "2026-06-10T14:46:21Z",
          "number": "1",
          "summary": "Current version"
        },
        {
          "date": "2026-09-16T09:07:15Z",
          "number": "2",
          "summary": "unknown changes"
        },
        {
          "date": "2026-09-16T20:37:20Z",
          "number": "3",
          "summary": "unknown changes"
        },
        {
          "date": "2026-09-16T21:40:01Z",
          "number": "4",
          "summary": "unknown changes"
        },
        {
          "date": "2026-09-17T17:34:45Z",
          "number": "5",
          "summary": "unknown changes"
        }
      ],
      "status": "final",
      "version": "5"
    }
  },
  "product_tree": {
    "branches": [
      {
        "branches": [
          {
            "branches": [
              {
                "category": "product_version",
                "name": "apptainer-leap-0:1.5.1-bp160.1.1.noarch",
                "product": {
                  "name": "apptainer-leap-0:1.5.1-bp160.1.1.noarch",
                  "product_id": "apptainer-leap-0:1.5.1-bp160.1.1.noarch",
                  "product_identification_helper": {
                    "cpe": "cpe:2.3:a:lfprojects:apptainer:1.5.1:*:*:*:*:go:*:*",
                    "purl": "pkg:rpm/suse/apptainer-leap@1.5.1-bp160.1.1?arch=noarch\u0026upstream=apptainer-0:1.5.1-bp160.1.1.src.rpm"
                  }
                }
              }
            ],
            "category": "architecture",
            "name": "noarch"
          },
          {
            "branches": [
              {
                "category": "product_version",
                "name": "apptainer-0:1.5.1-bp160.1.1.x86_64",
                "product": {
                  "name": "apptainer-0:1.5.1-bp160.1.1.x86_64",
                  "product_id": "apptainer-0:1.5.1-bp160.1.1.x86_64",
                  "product_identification_helper": {
                    "cpe": "cpe:2.3:a:lfprojects:apptainer:1.5.1:*:*:*:*:go:*:*",
                    "purl": "pkg:rpm/suse/apptainer@1.5.1-bp160.1.1?arch=x86_64\u0026upstream=apptainer-0:1.5.1-bp160.1.1.src.rpm"
                  }
                }
              }
            ],
            "category": "architecture",
            "name": "x86_64"
          },
          {
            "branches": [
              {
                "category": "product_name",
                "name": "openSUSE Leap 16.0",
                "product": {
                  "name": "openSUSE Leap 16.0",
                  "product_id": "openSUSE Leap 16.0"
                }
              }
            ],
            "category": "product_family",
            "name": "SUSE Linux Enterprise"
          }
        ],
        "category": "vendor",
        "name": "SUSE"
      }
    ],
    "relationships": [
      {
        "category": "default_component_of",
        "full_product_name": {
          "name": "apptainer-0:1.5.1-bp160.1.1.x86_64 as component of openSUSE Leap 16.0",
          "product_id": "openSUSE Leap 16.0:apptainer-0:1.5.1-bp160.1.1.x86_64"
        },
        "product_reference": "apptainer-0:1.5.1-bp160.1.1.x86_64",
        "relates_to_product_reference": "openSUSE Leap 16.0"
      },
      {
        "category": "default_component_of",
        "full_product_name": {
          "name": "apptainer-leap-0:1.5.1-bp160.1.1.noarch as component of openSUSE Leap 16.0",
          "product_id": "openSUSE Leap 16.0:apptainer-leap-0:1.5.1-bp160.1.1.noarch"
        },
        "product_reference": "apptainer-leap-0:1.5.1-bp160.1.1.noarch",
        "relates_to_product_reference": "openSUSE Leap 16.0"
      }
    ]
  },
  "vulnerabilities": [
    {
      "cve": "CVE-2026-48785",
      "ids": [
        {
          "system_name": "SUSE CVE Page",
          "text": "https://www.suse.com/security/cve/CVE-2026-48785"
        }
      ],
      "notes": [
        {
          "category": "general",
          "text": "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\u0027s 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.",
          "title": "CVE description"
        }
      ],
      "product_status": {
        "recommended": [
          "openSUSE Leap 16.0:apptainer-0:1.5.1-bp160.1.1.x86_64",
          "openSUSE Leap 16.0:apptainer-leap-0:1.5.1-bp160.1.1.noarch"
        ]
      },
      "references": [
        {
          "category": "external",
          "summary": "CVE-2026-48785",
          "url": "https://www.suse.com/security/cve/CVE-2026-48785"
        },
        {
          "category": "external",
          "summary": "SUSE Bug 1267982 for CVE-2026-48785",
          "url": "https://bugzilla.suse.com/1267982"
        }
      ],
      "remediations": [
        {
          "category": "vendor_fix",
          "details": "To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or \"zypper patch\".\n",
          "product_ids": [
            "openSUSE Leap 16.0:apptainer-0:1.5.1-bp160.1.1.x86_64",
            "openSUSE Leap 16.0:apptainer-leap-0:1.5.1-bp160.1.1.noarch"
          ]
        }
      ],
      "scores": [
        {
          "cvss_v3": {
            "baseScore": 4.8,
            "baseSeverity": "MEDIUM",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L",
            "version": "3.1"
          },
          "products": [
            "openSUSE Leap 16.0:apptainer-0:1.5.1-bp160.1.1.x86_64",
            "openSUSE Leap 16.0:apptainer-leap-0:1.5.1-bp160.1.1.noarch"
          ]
        }
      ],
      "threats": [
        {
          "category": "impact",
          "date": "2026-06-10T14:46:21Z",
          "details": "moderate"
        }
      ],
      "title": "CVE-2026-48785"
    }
  ]
}