Victim-authorized file overwrite via symlink race
Published Sep 7, 2026 · Updated Sep 8, 2026
Symlink following in GLib2 on affected Red Hat products allows local users to overwrite or create victim-writable files through a race. The handle_overwrite_open() fallback unlinks the destination after temporary-file creation fails, then recreates it without exclusive creation or symlink protection. Exploitation requires write access to the destination directory, the uncommon fallback path, and winning the race; success redirects a victim process write to a file that process can modify.
Summary
What happened
Symlink following in GLib2 on affected Red Hat products allows local users to overwrite or create victim-writable files through a race. The handle_overwrite_open() fallback unlinks the destination after temporary-file creation fails, then recreates it without exclusive creation or symlink protection. Exploitation requires write access to the destination directory, the uncommon fallback path, and winning the race; success redirects a victim process write to a file that process can modify.
The record
- CVE
- CVE-2026-86469
- Published
- Sep 7, 2026
- Updated
- Sep 8, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Enterprise Linux 6
- Classifications
- CWE-59
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 7, 2026CVE publishedPublication date reported by the CVE source.
- Sep 8, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
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