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.)
{
"license": "CC-BY-4.0",
"sources": [
{
"modified": "2026-06-17T03:45:53.453Z",
"database_specific": {
"status": "Modified"
},
"published": "2021-03-11T22:15:12.777Z",
"imported": "2026-07-17T20:39:18.454Z",
"url": "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2021-28153",
"id": "CVE-2021-28153",
"html_url": "https://nvd.nist.gov/vuln/detail/CVE-2021-28153"
}
]
}