Arbitrary file ownership via smart_rename symlink race
Published Mar 26, 2021 · Updated Dec 3, 2025
Symlink race in GNU Binutils 2.35 and earlier allows local users to gain ownership of arbitrary files through privileged utilities. The shared smart_rename() output path used by ar, objcopy, strip, and ranlib accepts a symlink destination while file replacement and ownership handling remain exposed to a race. Exploitation requires an unprivileged local user to influence the destination while a privileged user or script runs one of the affected utilities.
Summary
What happened
Symlink race in GNU Binutils 2.35 and earlier allows local users to gain ownership of arbitrary files through privileged utilities. The shared smart_rename() output path used by ar, objcopy, strip, and ranlib accepts a symlink destination while file replacement and ownership handling remain exposed to a race. Exploitation requires an unprivileged local user to influence the destination while a privileged user or script runs one of the affected utilities.
The record
- CVE
- CVE-2021-20197
- Published
- Mar 26, 2021
- Updated
- Dec 3, 2025
- Vendor
- The GnuPG Project
- Product
- GNU Binutils
- Classifications
- CWE-59, CWE-362, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 26, 2021CVE publishedPublication date reported by the CVE source.
- Dec 3, 2025Record 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=binutils 2.35
What conditions does exploitation require?
What is affected?
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