Arbitrary file overwrite via symlink TOCTOU race
Published Apr 20, 2026 · Updated Apr 20, 2026
TOCTOU race in GNU sed 4.1e through 4.9 allows local users to overwrite files through an attacker-controlled symlink swap. The open_next_file() function records the resolved output path through follow_symlink(), while ck_fopen() opens the original symlink path for input. Exploitation requires in-place editing with --follow-symlinks on an attacker-influenced path during the race window; resulting writes carry sed process permissions.
Summary
What happened
TOCTOU race in GNU sed 4.1e through 4.9 allows local users to overwrite files through an attacker-controlled symlink swap. The open_next_file() function records the resolved output path through follow_symlink(), while ck_fopen() opens the original symlink path for input. Exploitation requires in-place editing with --follow-symlinks on an attacker-influenced path during the race window; resulting writes carry sed process permissions.
The record
- CVE
- CVE-2026-5958
- Published
- Apr 20, 2026
- Updated
- Apr 20, 2026
- Vendor
- The GnuPG Project
- Product
- GNU sed
- Classifications
- CWE-367, CAPEC-27, CAPEC-29, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 20, 2026CVE publishedPublication date reported by the CVE source.
- Apr 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.1e <4.10
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo