An issue was discovered in GNOME GLib before 2.66.8. When gfilereplace() is used with GFILECREATEREPLACEDESTINATION 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": [
{
"published": "2021-03-11T22:15:12.777Z",
"html_url": "https://nvd.nist.gov/vuln/detail/CVE-2021-28153",
"url": "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2021-28153",
"id": "CVE-2021-28153",
"imported": "2025-10-19T21:13:23.544Z",
"modified": "2024-11-21T05:59:11.820Z"
}
]
}