published 28 Jan 2025 · updated 16 Nov 2026
Vulnerability when creating log files in github.com/golang/glog
7.1HighCVSS 7.1EPSS 0%
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 1.2.4.
When logs are written to a widely-writable directory (the default), an unprivileged attacker may predict a privileged process's log file path and pre-create a symbolic link to a sensitive file in its place. When that privileged process runs, it will follow the planted symlink and overwrite that sensitive file. To fix that, glog now causes the program to exit (with status code 2) when it finds that the configured log file already exists.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| github.com/golang/glog | <1.2.4 | 1.2.4 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket