Vulnerability in GNU Sed
CVE-2026-5958
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.
Vulnerability class: TOCTOU (Time-of-Check to Time-of-Use)
Published · last modified .
EPSS exploit prediction
EPSS: 0.001 (2.6th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 3rd percentile — 2.6% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.001 · newest: 0.001 · change: -0.000
Affected products
- GNU Sed — versions 4.1e
Weakness classification (CWE)
References
- www.gnu.org/software/sed/ (product)
- cert.pl/en/posts/2026/04/CVE-2026-5958 (third-party-advisory)
- af854a3a-2127-422b-91ae-364da2661108