os.OpenFile(path, os.O_CREATE|O_EXCL) behaved differently on Unix and Windows systems when the target path was a dangling symlink. On Unix systems, OpenFile with O_CREATE and O_EXCL flags never follows symlinks. On Windows, when the target path was a symlink to a nonexistent location, OpenFile would create a file in that location. OpenFile now always returns an error when the O_CREATE and O_EXCL flags are both set and the target path is a symlink.
References
| Link | Resource |
|---|---|
| https://go.dev/cl/672396 | Issue Tracking |
| https://go.dev/issue/73702 | Issue Tracking |
| https://groups.google.com/g/golang-announce/c/ufZ8WpEsA3A | Mailing List |
| https://pkg.go.dev/vuln/GO-2025-3750 | Vendor Advisory |
Configurations
Configuration 1 (hide)
| AND |
|
History
No history.
Information
Published : 2025-06-11 18:15
Updated : 2025-08-08 14:53
NVD link : CVE-2025-0913
Mitre link : CVE-2025-0913
CVE.ORG link : CVE-2025-0913
JSON object : View
Products Affected
microsoft
- windows
golang
- go
CWE
CWE-59
Improper Link Resolution Before File Access ('Link Following')
