Security update for apptainer
This update for apptainer fixes the following issues - CVE-2026-24137: github.com/sigstore/sigstore/pkg/tuf: legacy TUF client allows for arbitrary file writes with target cache path traversal (bsc#1264177). - CVE-2026-33186: google.golang.org/grpc: authorization bypass due to improper validation of the HTTP/2: path pseudo- header (bsc#1260311). - CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265844). - CVE-2026-34986: github.com/go-jose/go-jose/v4,github.com/go-jose/go-jose/v3: crafted JWE input with a missing encrypted key can lead to a denial of service (bsc#1262956). - CVE-2026-39821: golang.org/x/net/idna: failure to reject ASCII-only Punycode-encoded labels allows for validation bypass and privilege escalation (bsc#1266656). - CVE-2026-39827: memory leak when rejecting channels can lead to DoS in golang.org/x/crypto/ssh (bsc#1266202). - CVE-2026-39828: bypass of certificate restrictions in golang.org/x/crypto/ssh (bsc#1266202). - CVE-2026-39829: pathological RSA/DSA parameters may cause DoS in golang.org/x/crypto/ssh (bsc#1266202). - CVE-2026-39830: client can cause server deadlock on unexpected responses in golang.org/x/crypto/ssh (bsc#1266202). - CVE-2026-39831: bypass of FIDO/U2F security keys physical interaction in golang.org/x/crypto/ssh (bsc#1266202). - CVE-2026-39832: agent constraints dropped when forwarding keys in golang.org/x/crypto/ssh/agent (bsc#1266202). - CVE-2026-39833: key constraints not enforced in golang.org/x/crypto/ssh/agent (bsc#1266202). - CVE-2026-39834: infinite loop on large channel writes in golang.org/x/crypto/ssh (bsc#1266202). - CVE-2026-39835: server panic during CheckHostKey/Authenticate in golang.org/x/crypto/ssh (bsc#1266202). - CVE-2026-42508: auth bypass via unenforced @revoked status in golang.org/x/crypto/ssh/knownhosts (bsc#1266202). - CVE-2026-46595: VerifiedPublicKeyCallback permissions skip enforcement in golang.org/x/crypto/ssh (bsc#1266202). - CVE-2026-46597: byte arithmetic causes underflow and panic in golang.org/x/crypto/ssh (bsc#1266202). - CVE-2026-46598: pathological inputs can lead to client panic in golang.org/x/crypto/ssh/agent (bsc#1266202). - CVE-2026-48785: incorrect path matching for limit container paths directive (bsc#1267982). Changes for apptainer: - Update apptainer to version v1.5.1 * Work around segmentation fault sometimes seen while `mksquashfs` under proot is creating a SIF file. * Update bundled PRoot to version 5.4.0-rootless.3 in order to fix a problem where SIF files could be corrupted when `mksquashfs` died with a signal. The proot command was not passing back an error exit code. * Updated bundled `squashfuse_ll` to version 0.6.2 in order to fix a crash sometimes seen with apptainer in unprivileged docker. * Update bundled fuse2fs to version 1.47.4 instead of patching the bugs in 1.47.3. * Fix a crash that happened when `/etc/resolv.conf` was a symlink while building from a definition file using the localimage bootstrap. * Support hosts that have an /etc/resolv.conf symlink pointing to `../run` in addition to `/run`. * Change the download-dependencies script to skip downloading the PRoot source code on architectures that it is known to not support (that is: ppc*, s390*, and riscv*). In those situations Apptainer will skip trying to compile and run proot. As a result original owners and groups of files will not be preserved in SIF images built by unprivileged users, as was the case for all architectures prior to 1.5.0. * Fix panic encountered during progress bar update while pulling image. * Fix fakeroot overwriting root's username in `/etc/passwd` with the host user's name, a regression introduced in v1.5.0. * Add nonested flag for --mount specifications to prevent individual bind mounts from being passed to nested containers via `APPTAINER_BIND`.
02 / AFFECTED SOFTWARE
Affected packages
03 / CONNECTIONS
Connected vulnerabilities
04 / EVIDENCE
Source records
This update for apptainer fixes the following issues - CVE-2026-24137: github.com/sigstore/sigstore/pkg/tuf: legacy TUF client allows for arbitrary file writes with target cache path traversal (bsc#1264177). - CVE-2026-33186: google.golang.org/grpc: authorization bypass due to improper validation of the HTTP/2: path pseudo- header (bsc#1260311). - CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265844). - CVE-2026-34986: github.com/go-jose/go-jose/v4,github.com/go-jose/go-jose/v3: crafted JWE input with a missing encrypted key can lead to a denial of service (bsc#1262956). - CVE-2026-39821: golang.org/x/net/idna: failure to reject ASCII-only Punycode-encoded labels allows for validation bypass and privilege escalation (bsc#1266656). - CVE-2026-39827: memory leak when rejecting channels can lead to DoS in golang.org/x/crypto/ssh (bsc#1266202). - CVE-2026-39828: bypass of certificate restrictions in golang.org/x/crypto/ssh (bsc#1266202). - CVE-2026-39829: pathological RSA/DSA parameters may cause DoS in golang.org/x/crypto/ssh (bsc#1266202). - CVE-2026-39830: client can cause server deadlock on unexpected responses in golang.org/x/crypto/ssh (bsc#1266202). - CVE-2026-39831: bypass of FIDO/U2F security keys physical interaction in golang.org/x/crypto/ssh (bsc#1266202). - CVE-2026-39832: agent constraints dropped when forwarding keys in golang.org/x/crypto/ssh/agent (bsc#1266202). - CVE-2026-39833: key constraints not enforced in golang.org/x/crypto/ssh/agent (bsc#1266202). - CVE-2026-39834: infinite loop on large channel writes in golang.org/x/crypto/ssh (bsc#1266202). - CVE-2026-39835: server panic during CheckHostKey/Authenticate in golang.org/x/crypto/ssh (bsc#1266202). - CVE-2026-42508: auth bypass via unenforced @revoked status in golang.org/x/crypto/ssh/knownhosts (bsc#1266202). - CVE-2026-46595: VerifiedPublicKeyCallback permissions skip enforcement in golang.org/x/crypto/ssh (bsc#1266202). - CVE-2026-46597: byte arithmetic causes underflow and panic in golang.org/x/crypto/ssh (bsc#1266202). - CVE-2026-46598: pathological inputs can lead to client panic in golang.org/x/crypto/ssh/agent (bsc#1266202). - CVE-2026-48785: incorrect path matching for limit container paths directive (bsc#1267982). Changes for apptainer: - Update apptainer to version v1.5.1 * Work around segmentation fault sometimes seen while `mksquashfs` under proot is creating a SIF file. * Update bundled PRoot to version 5.4.0-rootless.3 in order to fix a problem where SIF files could be corrupted when `mksquashfs` died with a signal. The proot command was not passing back an error exit code. * Updated bundled `squashfuse_ll` to version 0.6.2 in order to fix a crash sometimes seen with apptainer in unprivileged docker. * Update bundled fuse2fs to version 1.47.4 instead of patching the bugs in 1.47.3. * Fix a crash that happened when `/etc/resolv.conf` was a symlink while building from a definition file using the localimage bootstrap. * Support hosts that have an /etc/resolv.conf symlink pointing to `../run` in addition to `/run`. * Change the download-dependencies script to skip downloading the PRoot source code on architectures that it is known to not support (that is: ppc*, s390*, and riscv*). In those situations Apptainer will skip trying to compile and run proot. As a result original owners and groups of files will not be preserved in SIF images built by unprivileged users, as was the case for all architectures prior to 1.5.0. * Fix panic encountered during progress bar update while pulling image. * Fix fakeroot overwriting root's username in `/etc/passwd` with the host user's name, a regression introduced in v1.5.0. * Add nonested flag for --mount specifications to prevent individual bind mounts from being passed to nested containers via `APPTAINER_BIND`.
05 / REFERENCES
Further evidence
- https://bugzilla.suse.com/1260311
- https://bugzilla.suse.com/1262956
- https://bugzilla.suse.com/1264177
- https://bugzilla.suse.com/1265844
- https://bugzilla.suse.com/1266202
- https://bugzilla.suse.com/1266656
- https://bugzilla.suse.com/1267982
- https://www.suse.com/security/cve/CVE-2026-24137
- https://www.suse.com/security/cve/CVE-2026-33186
- https://www.suse.com/security/cve/CVE-2026-33814
- https://www.suse.com/security/cve/CVE-2026-34986
- https://www.suse.com/security/cve/CVE-2026-39821
- https://www.suse.com/security/cve/CVE-2026-39827
- https://www.suse.com/security/cve/CVE-2026-39828
- https://www.suse.com/security/cve/CVE-2026-39829
- https://www.suse.com/security/cve/CVE-2026-39830
- https://www.suse.com/security/cve/CVE-2026-39831
- https://www.suse.com/security/cve/CVE-2026-39832
- https://www.suse.com/security/cve/CVE-2026-39833
- https://www.suse.com/security/cve/CVE-2026-39834
- https://www.suse.com/security/cve/CVE-2026-39835
- https://www.suse.com/security/cve/CVE-2026-42508
- https://www.suse.com/security/cve/CVE-2026-46595
- https://www.suse.com/security/cve/CVE-2026-46597
- https://www.suse.com/security/cve/CVE-2026-46598
- https://www.suse.com/security/cve/CVE-2026-48785
- https://www.suse.com/support/update/announcement/2026/suse-su-20262609-1/