CVE-2026-5958 | GNU sed up to 4.9 open_next_file toctou (EUVD-2026-23834)

VDB-358301 · CVE-2026-5958 · EUVD-2026-23834 GNU SED UP TO 4.9 OPEN_NEXT_FILE TOCTOU HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 2.4 $0-$5k 5.53+ Summaryinfo A vulnerability classified as problematic has been found in GNU sed up to 4.9. This impacts the function open_next_file. The manipulation leads to toctou. This vulnerability is documented as CVE-2026-5958. The attack needs to be performed locally. There is not any exploit available. It is recommended to upgrade the affected component. Detailsinfo A vulnerability, which was classified as problematic, has been found in GNU sed up to 4.9. This issue affects the function open_next_file. The manipulation with an unknown input leads to a toctou vulnerability. Using CWE to declare the problem leads to CWE-367. The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check. This can cause the product to perform invalid actions when the resource is in an unexpected state. Impacted is integrity. The summary by CVE is: 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. The weakness was released with AFINE Team. The advisory is shared at gnu.org. The identification of this vulnerability is CVE-2026-5958 since 04/09/2026. The exploitation is known to be difficult. An attack has to be approached locally. Technical details are known, but no exploit is available. Upgrading to version 4.10 eliminates this vulnerability. The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-23834). Productinfo Vendor GNU Name sed Version 4.0 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 License open-source Website Vendor: https://www.gnu.org/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 2.5 VulDB Meta Temp Score: 2.4 VulDB Base Score: 2.5 VulDB Temp Score: 2.4 VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Toctou CWE: CWE-367 / CWE-362 CAPEC: 🔒 ATT&CK: 🔒 Physical: Partially Local: Yes Remote: No Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: sed 4.10 Timelineinfo 04/09/2026 CVE reserved 04/20/2026 +11 days Advisory disclosed 04/20/2026 +0 days VulDB entry created 04/20/2026 +0 days VulDB entry last update Sourcesinfo Vendor: gnu.org Advisory: gnu.org Organization: AFINE Team Status: Confirmed CVE: CVE-2026-5958 (🔒) GCVE (CVE): GCVE-0-2026-5958 GCVE (VulDB): GCVE-100-358301 EUVD: 🔒 Entryinfo Created: 04/20/2026 14:37 Updated: 04/20/2026 15:55 Changes: 04/20/2026 14:37 (67), 04/20/2026 15:55 (1) Complete: 🔍 Cache ID: 99:0E9:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸