Описание
Security update for sed
This update for sed fixes the following issue:
- CVE-2026-5958: a TOCTOU race can allow to read attacker-controlled content and write it to an unintended file (bsc#1262144).
Список пакетов
Container bci/bci-init:latest
Container bci/bci-sle15-kernel-module-devel:latest
Container bci/openjdk-devel:17
Container bci/openjdk-devel:21
Container bci/openjdk-devel:latest
Container bci/openjdk:17
Container bci/openjdk:21
Container bci/openjdk:latest
Container suse/kea:2.6
Container suse/kiosk/firefox-esr:latest
Container suse/kiosk/pulseaudio:latest
Container suse/kiosk/xorg-client:latest
Container suse/kiosk/xorg:latest
Container suse/manager/5.0/x86_64/server:latest
Container suse/mariadb:latest
Container suse/multi-linux-manager/5.1/x86_64/proxy-httpd:latest
Container suse/multi-linux-manager/5.1/x86_64/proxy-salt-broker:latest
Container suse/multi-linux-manager/5.1/x86_64/proxy-squid:latest
Container suse/multi-linux-manager/5.1/x86_64/server-hub-xmlrpc-api:latest
Container suse/multi-linux-manager/5.1/x86_64/server-saline:latest
Container suse/multi-linux-manager/5.1/x86_64/server:latest
Container suse/postgres:16
Container suse/postgres:16.14
Container suse/postgres:17
Container suse/postgres:17.10
Container suse/postgres:latest
Container suse/sle15:latest
Container third-party/amd/amdgpu-driver:sles-15.7-30.20.1
Container third-party/amd/amdgpu-driver:sles-15.7-30.30.3
Container third-party/amd/amdgpu-driver:sles-15.7-31.10
Container third-party/amd/amdgpu-driver:sles-15.7-31.20
Container third-party/amd/amdgpu-driver:sles-15.7-31.30
Container third-party/nvidia/driver:550-sles15.7
Container third-party/nvidia/driver:570-sles15.7
Container third-party/nvidia/driver:575-sles15.7
Container third-party/nvidia/driver:580-sles15.7
Container third-party/nvidia/driver:590-sles15.7
Container third-party/nvidia/driver:595-sles15.7
Image SLES15-SP6
Image SLES15-SP6-Azure-3P
Image SLES15-SP6-Azure-Basic
Image SLES15-SP6-Azure-Standard
Image SLES15-SP6-BYOS
Image SLES15-SP6-BYOS-Azure
Image SLES15-SP6-BYOS-EC2
Image SLES15-SP6-BYOS-GCE
Image SLES15-SP6-CHOST-BYOS
Image SLES15-SP6-CHOST-BYOS-Aliyun
Image SLES15-SP6-CHOST-BYOS-Azure
Image SLES15-SP6-CHOST-BYOS-EC2
Image SLES15-SP6-CHOST-BYOS-GCE
Image SLES15-SP6-CHOST-BYOS-GDC
Image SLES15-SP6-CHOST-BYOS-SAP-CCloud
Image SLES15-SP6-EC2
Image SLES15-SP6-EC2-ECS-HVM
Image SLES15-SP6-GCE
Image SLES15-SP6-HPC
Image SLES15-SP6-HPC-Azure
Image SLES15-SP6-HPC-BYOS
Image SLES15-SP6-HPC-BYOS-Azure
Image SLES15-SP6-HPC-BYOS-EC2
Image SLES15-SP6-HPC-BYOS-GCE
Image SLES15-SP6-HPC-EC2
Image SLES15-SP6-HPC-GCE
Image SLES15-SP6-Hardened-BYOS
Image SLES15-SP6-Hardened-BYOS-Azure
Image SLES15-SP6-Hardened-BYOS-EC2
Image SLES15-SP6-Hardened-BYOS-GCE
Image SLES15-SP6-SAP
Image SLES15-SP6-SAP-Azure
Image SLES15-SP6-SAP-Azure-3P
Image SLES15-SP6-SAP-BYOS
Image SLES15-SP6-SAP-BYOS-Azure
Image SLES15-SP6-SAP-BYOS-EC2
Image SLES15-SP6-SAP-BYOS-GCE
Image SLES15-SP6-SAP-EC2
Image SLES15-SP6-SAP-GCE
Image SLES15-SP6-SAP-Hardened
Image SLES15-SP6-SAP-Hardened-Azure
Image SLES15-SP6-SAP-Hardened-BYOS
Image SLES15-SP6-SAP-Hardened-BYOS-Azure
Image SLES15-SP6-SAP-Hardened-BYOS-EC2
Image SLES15-SP6-SAP-Hardened-BYOS-GCE
Image SLES15-SP6-SAP-Hardened-EC2
Image SLES15-SP6-SAP-Hardened-GCE
Image SLES15-SP6-SAPCAL
Image SLES15-SP6-SAPCAL-Azure
Image SLES15-SP6-SAPCAL-EC2
Image SLES15-SP6-SAPCAL-GCE
Image SLES15-SP7-Azure-3P
Image SLES15-SP7-Azure-Basic
Image SLES15-SP7-Azure-Standard
Image SLES15-SP7-BYOS-Azure
Image SLES15-SP7-BYOS-EC2
Image SLES15-SP7-BYOS-GCE
Image SLES15-SP7-CHOST-BYOS-Aliyun
Image SLES15-SP7-CHOST-BYOS-Azure
Image SLES15-SP7-CHOST-BYOS-EC2
Image SLES15-SP7-CHOST-BYOS-GCE
Image SLES15-SP7-CHOST-BYOS-GDC
Image SLES15-SP7-CHOST-BYOS-SAP-CCloud
Image SLES15-SP7-EC2
Image SLES15-SP7-EC2-ECS-HVM
Image SLES15-SP7-GCE
Image SLES15-SP7-GCE-3P
Image SLES15-SP7-HPC-Azure
Image SLES15-SP7-HPC-BYOS-Azure
Image SLES15-SP7-HPC-BYOS-EC2
Image SLES15-SP7-HPC-BYOS-GCE
Image SLES15-SP7-Hardened-BYOS-Azure
Image SLES15-SP7-Hardened-BYOS-EC2
Image SLES15-SP7-Hardened-BYOS-GCE
Image SLES15-SP7-SAP-Azure
Image SLES15-SP7-SAP-Azure-3P
Image SLES15-SP7-SAP-BYOS-Azure
Image SLES15-SP7-SAP-BYOS-EC2
Image SLES15-SP7-SAP-BYOS-GCE
Image SLES15-SP7-SAP-EC2
Image SLES15-SP7-SAP-GCE
Image SLES15-SP7-SAP-GCE-3P
Image SLES15-SP7-SAP-Hardened-Azure
Image SLES15-SP7-SAP-Hardened-BYOS-Azure
Image SLES15-SP7-SAP-Hardened-BYOS-EC2
Image SLES15-SP7-SAP-Hardened-BYOS-GCE
Image SLES15-SP7-SAP-Hardened-GCE
Image SLES15-SP7-SAPCAL-Azure
Image SLES15-SP7-SAPCAL-EC2
Image SLES15-SP7-SAPCAL-GCE
Image proxy-squid-image
Image server-attestation-image
Image server-hub-xmlrpc-api-image
Image server-image-sles15sp7
Image server-saline-image
SUSE Linux Enterprise Module for Basesystem 15 SP7
Ссылки
- Link for SUSE-SU-2026:1941-1
- E-Mail link for SUSE-SU-2026:1941-1
- SUSE Security Ratings
- SUSE Bug 1262144
- SUSE CVE CVE-2026-5958 page
Описание
When sed is invoked with both -i (in-place edit) and --follow-symlinks, the function open_next_file() performs two separate, non-atomic filesystem operations on the same path: 1. resolves symlink to its target and stores the resolved path for determining when output is written, 2. opens the original symlink path (not the resolved one) to read the file. Between these two calls there is a race window. If an attacker atomically replaces the symlink with a different target during that window, sed will: read content from the new (attacker-chosen) symlink target and write the processed result to the path recorded in step 1. This can lead to arbitrary file overwrite with attacker-controlled content in the context of the sed process. This issue was fixed in version 4.10.
Затронутые продукты
Ссылки
- CVE-2026-5958
- SUSE Bug 1262144