An issue was discovered in GNOME GLib before 2.66.8. When g_file_replace() is used with G_FILE_CREATE_REPLACE_DESTINATION to replace a path that is a dangling symlink, it incorrectly also creates the target of the symlink as an empty file, which could conceivably have security relevance if the symlink is attacker-controlled. (If the path is a symlink to a file that already exists, then the contents of that file correctly remain unchanged.)
Metrics
Affected Vendors & Products
References
History
Wed, 14 Oct 2026 12:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Status: PUBLISHED
Assigner: mitre
Published: 2021-03-11T21:04:15.000Z
Updated: 2026-10-14T11:39:29.929Z
Reserved: 2021-03-11T00:00:00.000Z
Link: CVE-2021-28153
No data.
Status : Modified
Published: 2021-03-11T22:15:12.777
Modified: 2026-10-14T12:17:10.900
Link: CVE-2021-28153